Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Pulumi Cloud (BYOK) — connector documentation

  • MCP endpoint: https://byok-pulumi.connectorbay.com/mcp
  • REST API: POST https://byok-pulumi.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-pulumi.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Pulumi Cloud Pulumi access token (pul-...), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-pulumi.connectorbay.com/health · Tool schemas: https://byok-pulumi.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-pulumi · agent@connectorbay.com

What Pulumi Cloud (BYOK) is for

Pulumi Cloud (BYOK) lets an AI assistant read your own Pulumi Cloud data through the Pulumi Cloud API with a key you supply (Pulumi access token (pul-...)). Read-only: 12 tools (get_current_user, list_my_stacks, get_stack, get_latest_update, get_update_summary, count_stack_resources, list_org_members, list_teams, list_org_deployments, list_esc_environments, list_audit_logs, list_registry_packages). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.pulumi.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Pulumi Cloud. Pulumi Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Pulumi account and organizations does my token belong to?"
  • "Which Pulumi stacks do I have in the acme organization?"
  • "What is the state of the acme/web-app/prod Pulumi stack?"
  • "Did the last Pulumi update of acme/web-app/prod succeed?"
  • "How did update 11 of acme/web-app/prod finish?"
  • "How many resources does acme/web-app/prod manage?"

What it does

  • get_current_user: Show the Pulumi Cloud account the token belongs to: id, name, GitHub login, email, MFA flag and organization memberships with roles.
  • list_my_stacks: List stacks the token can access with organization, project, stack name, last update time (Unix seconds) and resource count. Filter by organization, project or tag.
  • get_stack: Get one stack: current version, tags, active update id and any operation currently running.
  • get_latest_update: Get the most recent update of a stack: kind (update, preview, refresh, destroy), result, message, start and end times and resource changes.
  • get_update_summary: Get a short summary of one stack update by version number: result, start and end time and resource count.
  • count_stack_resources: Get how many resources the stack currently manages, from its most recent update.
  • list_org_members: List the members of an organization with role, join date, suspension flag and the user's name, GitHub login and email.
  • list_teams: List the teams of an organization with name, display name, kind (pulumi, github or scim) and description.
  • list_org_deployments: List Pulumi Deployments runs across an organization with stack, operation (update, preview, destroy, refresh), status and times.
  • list_esc_environments: List Pulumi ESC environments of an organization with project, name and created and modified times (values are not read).
  • list_audit_logs: List organization audit log events with time, event type, description, actor and token name. Times are Unix seconds.
  • list_registry_packages: Search the Pulumi Registry for providers and components by text, with publisher, version, description and repository URL.

BYOK key

You bring your own Pulumi Cloud Pulumi access token (pul-...) (https://app.pulumi.com/account/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.pulumi.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Pulumi Cloud API (api.pulumi.com) with a BYOK key; documentation: https://www.pulumi.com/docs/reference/service-rest-api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Pulumi Cloud. Pulumi Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Pulumi Cloud account.

Built for: Worldwide. Languages: English.