# Pulumi MCP connector

The Pulumi connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent list your Pulumi organizations and projects, manage change gates and start applies, with each person signed in as themselves and every call logged.

Source: https://elaichi.ai/connectors/pulumi/

## Facts

| | |
| --- | --- |
| Application | Pulumi |
| Category | Application Development |
| AI tools | 381 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Pulumi is connected

- List every project in our platform Pulumi organization
- Create a change gate on the production project before Friday's apply
- Which Pulumi CLI versions are our teams running right now?

## Connect Pulumi in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Pulumi.
2. Optionally set Share with, then press Connect.
3. Paste a Pulumi API key. One person generates a token in Pulumi and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Pulumi tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Pulumi MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Pulumi MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Pulumi MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Pulumi MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Pulumi MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Pulumi to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Pulumi tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Pulumi through Elaichi

### Find the right project before anyone touches it

Platform engineering. Ask which Pulumi organizations and projects exist and get the list back in chat. Pick the right one before an apply ever starts.

### Start a Pulumi apply from chat

DevOps. Kick off an apply for a project without opening a terminal. The audit log records who started it and when.

### Put a change gate in front of production

Security. Create or update a Pulumi change gate so a risky change waits for review, then remove it once the window closes.

### Check which CLI versions teams are running

Release management. Pull the list of Pulumi CLI versions ahead of a rollout so you know who is behind before it matters.

### Link Azure DevOps or Bitbucket to Pulumi

Engineering. Set up or review the connection between a Pulumi organization and Azure DevOps or Bitbucket, and check access status when a pipeline stalls.

### Onboard a new Pulumi agent without passing keys

IT. Create a Pulumi agent signup, submit the claim and check its status, all from the same chat and without handing anyone a credential.

## Elaichi vs Zapier MCP vs Composio for Pulumi

All three can connect Pulumi to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Pulumi tools | Allow or restrict single Pulumi tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Pulumi call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Pulumi to Claude?

Connect Pulumi in Elaichi by pasting a Pulumi API key, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Pulumi and no client ID or secret to generate. Claude signs you in through Elaichi and your Pulumi projects, change gates and applies are available in the next conversation.

### Does Pulumi work with ChatGPT and Cursor as well as Claude?

Yes. Once Pulumi is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Pulumi once and every client sees the same connection.

### What can an AI agent actually do with my Pulumi data?

An agent connected to Pulumi can list your organizations and projects, create, update or delete change gates, start an apply, check which Pulumi CLI versions are in use, review the links to Azure DevOps and Bitbucket, and handle Pulumi agent signups and claims. Short concrete asks, like "list the projects in our platform organization", work better than long sentences.

### Does connecting Pulumi give the AI access to every organization and project?

No. Every call into Pulumi runs under the access of the person who signed in, so an agent sees only the Pulumi organizations, projects and change gates that person can already reach. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Pulumi itself allows.

### Can my team share one Pulumi connection?

Yes. One person connects Pulumi in Elaichi and shares the connection with a team, and nobody else ever handles the Pulumi API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every apply or change gate edit.

### Can I stop an agent from deleting or changing things in Pulumi?

Yes. Restrictions in Elaichi apply per action, so you can restrict deleting a Pulumi change gate or starting an apply for a role or for one person. A restricted Pulumi tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Pulumi connection when someone leaves?

Offboarding a person in Elaichi ends their Pulumi access at once, in every client they used. A Pulumi connection that was shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting Pulumi once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Pulumi MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Pulumi is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Pulumi?

Yes. Both let Claude, ChatGPT or Cursor use Pulumi. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Pulumi call.

### How is Elaichi different from Composio for Pulumi?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Pulumi: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 381 Pulumi tools

Every tool below is callable through https://api.elaichi.ai/mcp once Pulumi is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Pulumi agents signups** (List). Get a proof-of-work challenge for Pulumi agent signup. Returns the challengeID and the challengeData the proof of work is computed over. The challenge expires after a short window if not consumed.
- **Create a Pulumi agents signup** (Create). Create a new Pulumi Cloud account programmatically for an agent. Returns: accessToken, accessTokenValidUntil, claimToken, claimTokenValidUntil, userInfo. The account is created in a pre-claim state; the human takes ownership via the returned claim URL. Required: challengeID, challengeResult.
- **Get single Pulumi signup validate by ID** (Get). Validate an agent signup claim token in Pulumi Cloud. Verifies the token is still valid and returns the agent claim response (AgentClaimResponse) — details about the agent and the resources it created; upstream docs do not enumerate its fields. 404 if unknown, expired, or canceled. Required: id.
- **Create a Pulumi agent claim** (Create). Preview (dryRun=true) or commit a Pulumi agent claim for an organization. On commit the agent's stacks transfer to the destination organization and the agent's organization and access token are soft-deleted; conflicts or failures are returned and block the change. Returns: agent, conflicts, failures, and 3 more. Required: org_name, claimToken.
- **List all Pulumi claim status** (List). Fetch details about recent Pulumi agent claims for an organization. Returns a JSON claim status object whose fields follow the upstream AgentClaimsStatus schema. Required: org_name.
- **List all Pulumi capabilities** (List). List the set of capabilities that the Pulumi Cloud service supports. Requires no parameters. Returns: capability, configuration, version.
- **List all Pulumi change gates** (List). List change gates in a Pulumi Cloud organization, currently for a single entity. Returns matching change gate objects with id and content-type-specific attributes. Required: org_name. Supports optional entityType and qualifiedName filters.
- **Create a Pulumi change gate** (Create). Create a change gate in a Pulumi Cloud organization that enforces approval requirements before changes can be applied to a protected entity. Returns the created change gate as an opaque object with id and content-type-specific attributes. Required: org_name, enabled, name, rule, target.
- **Get single Pulumi change gate by ID** (Get). Get a single change gate by id in a Pulumi Cloud organization, including its approval requirements and the entity it protects. Returns the change gate as an opaque object with id and content-type-specific attributes. Required: id, org_name.
- **Update a Pulumi change gate by ID** (Update). Update the configuration of an existing change gate, such as its approval requirements or protected entity, in a Pulumi Cloud organization. Returns the updated change gate as an opaque object with id and content-type-specific attributes. Required: id, org_name, enabled, name, rule, target.
- **Delete a Pulumi change gate by ID** (Delete). Delete a change gate by id, removing the approval requirement from the protected entity so changes no longer require approval. Returns an empty 204 response on success. Required: id, org_name.
- **Create a Pulumi apply** (Create). Apply an approved Pulumi change request to execute its proposed infrastructure changes. Returns the apply result: id and schema-specific attributes per the upstream ChangeRequestApplyResult definition. The change request must have the required number of approvals; a conflict returns…. Required: org_name, change_request_id.
- **List all Pulumi cli versions** (List). Get version information about the Pulumi CLI. Returns: latestDevVersion, latestVersion, oldestWithoutWarning. Takes no required parameters.
- **List all Pulumi org integrations** (List). List a summary of all VCS integrations (GitHub, GitLab, Azure DevOps, Custom) configured for a Pulumi organization. Returns: avatarUrl, baseUrl, hasIndividualAccess, host, id, name, vcsProvider. Required: org_name.
- **List all Pulumi integrations azure devops** (List). List the Azure DevOps integrations configured for a Pulumi organization. Returns one integration record per item, each including its id; field-level detail beyond the id is not enumerated in the available documentation. Required: org_name.
- **Create a Pulumi integrations azure devop** (Create). Create an Azure DevOps integration for a Pulumi organization. Returns an empty 204 response on success. Required: org_name. The request body must specify the Azure DevOps organization and project; 409 is returned if an integration already exists for that project.
- **Get single Pulumi integrations azure devop by ID** (Get). Get a single Azure DevOps integration by id from a Pulumi organization. Returns the integration record including its id; field-level detail beyond the id is not enumerated in the available documentation. Required: id, org_name.
- **Update a Pulumi integrations azure devop by ID** (Update). Update an existing Azure DevOps integration's settings by id, including its Azure DevOps organization, project, or authentication configuration. Returns an empty 204 response on success. Required: id, org_name.
- **Delete a Pulumi integrations azure devop by ID** (Delete). Delete a specific Azure DevOps integration from a Pulumi organization by id. Returns an empty 204 response on success. Required: id, org_name.
- **List all Pulumi azure devops access status** (List). Get the current user's Azure DevOps access status for a Pulumi organization, including whether they have a valid OAuth token. Returns: availableOrgs, hasIntegration, hasUserToken. Required: org_name.
- **List all Pulumi setup organizations** (List). List the Azure DevOps organizations available to the current Pulumi user for VCS integration setup. Returns: accountUrl, hasRequiredPermissions, id, name. Requires an active Azure DevOps OAuth token. Required: org_name.
- **List all Pulumi organization projects** (List). List the Azure DevOps projects in an Azure DevOps organization that are available to the current user in Pulumi. Returns: id, name. Required: org_name, ado_org_name.
- **List all Pulumi integrations bitbuckets** (List). List the BitBucket integrations configured for a Pulumi organization. Returns: authType, authUser, avatarUrl, disableDetailedDiff, disableNeoSummaries, id, installed, valid, and 4 more. Entries carry the linked BitBucket workspace metadata and validity status, as typed by the upstream ListBitBucketIntegrationsResponse schema. Required: org_name.
- **Create a Pulumi integrations bitbucket** (Create). Create a BitBucket integration for a Pulumi organization. Requires a BitBucket workspace UUID and optionally configures authentication via the user's BitBucket OAuth token or a workspace access token / PAT. Returns an empty 204 response on success; the call fails if an integration already exists for the workspace. Required: org_name, workspaceSlug, workspaceUuid.
- **Get single Pulumi integrations bitbucket by ID** (Get). Get a single BitBucket integration by id. Returns: id, installed, valid, and 9 more. The record's full details — the linked BitBucket workspace, authentication configuration, and validity status — are typed by the upstream BitBucketIntegrationDetails schema, which the published reference does not enumerate field-by-field. Required: id, org_name.
- **Update a Pulumi integrations bitbucket by ID** (Update). Update a BitBucket integration's settings, such as PR comment preferences and AI summary options. Returns an empty 204 response on success. Required: id, org_name.
- **Delete a Pulumi integrations bitbucket by ID** (Delete). Delete a BitBucket integration by id, removing the integration and cleaning up its associated webhooks and access tokens. Returns an empty 204 response on success. Required: id, org_name.
- **List all Pulumi bitbucket access status** (List). Get a user's BitBucket access status in Pulumi for an organization, including whether they have a valid BitBucket OAuth token and which BitBucket workspaces are available for new integrations. Returns the BitBucketAccessStatusResponse object; the API reference does not enumerate its fields. Required: org_name.
- **List all Pulumi integrations customs** (List). List all custom VCS integrations configured for a Pulumi organization. Returns each integration's configuration, webhook URL, and configured repositories; webhook secrets are not included in list responses. Required: org_name.
- **Create a Pulumi integrations custom** (Create). Create a custom VCS integration connecting a self-hosted or third-party VCS (e.g. Gitea, Forgejo, Bitbucket Server) to Pulumi Deployments. Returns the created integration including its configuration, webhook URL, and one-time HMAC secret for signature verification. Required: org_name, baseUrl, environment, name.
- **Get single Pulumi integrations custom by ID** (Get). Get a specific custom VCS integration by id. Returns the integration details including its configuration, webhook URL, and configured repositories; the webhook secret is not included (it is returned only at creation time or when regenerated). Required: id, org_name.
- **Update a Pulumi integrations custom by ID** (Update). Update a custom VCS integration's settings by id; only provided fields are modified. Returns the updated integration (configuration, webhook URL, repositories). Set regenerateWebhookSecret to true to rotate the webhook HMAC secret, invalidating the previous secret immediately. Required: id, org_name.
- **Delete a Pulumi integrations custom by ID** (Delete). Delete a custom VCS integration by id, permanently removing the integration, its webhook endpoint, and all configured repository associations. Returns an empty 204 response on success. Required: id, org_name.
- **Create a Pulumi repo** (Create). Add a repository to a custom VCS integration in Pulumi Cloud. Returns an empty 204 response on success; a duplicate repository name is rejected. Required: org_name, integration_id, name.
- **List all Pulumi repos** (List). List repositories available through a Pulumi Cloud VCS integration. Returns the collection of repositories the integration exposes. Required: org_name, provider, integration_id.
- **Pulumi repos bulk delete** (Delete). Remove a repository from a custom VCS integration in Pulumi Cloud; the repository is identified by the name provided in the request body. Returns an empty 204 response on success. Required: org_name, integration_id, name.
- **List all Pulumi integrations githubs** (List). List the GitHub App integrations configured for a Pulumi organization. Returns: installationUrl, integrations. Required: org_name.
- **Create a Pulumi integrations github** (Create). Start GitHub App setup for a Pulumi organization. Returns the setup response carrying the installation URL and state for completing the GitHub App installation flow. Required: org_name.
- **Get single Pulumi integrations github by ID** (Get). Get a single GitHub App integration by id in a Pulumi organization. Returns: accountID, accountName, avatarUrl, created, disableCodeAccessForReviews, disableDetailedDiff, disableDraftPRComments, disableNeoSummaries, disablePRComments, ghUrls, hasContentsPermission, hasMembersPermission, id, individualAuthEnabled, and 4 more. Required: org_name, id.
- **Update a Pulumi integrations github by ID** (Update). Update a GitHub App integration's settings in a Pulumi organization. Returns an empty 204 response on success. Required: id, org_name.
- **Delete a Pulumi integrations github by ID** (Delete). Delete a GitHub App integration from a Pulumi organization. Returns an empty 204 response on success. Required: org_name, id.
- **List all Pulumi integrations github enterprises** (List). List all GitHub Enterprise Server integrations for a Pulumi organization; returns only self-hosted GitHub App installations. Returns: installationUrl, integrations. Required: org_name.
- **Get single Pulumi integrations github enterprise by ID** (Get). Get a specific GitHub Enterprise Server integration in a Pulumi organization by id. Returns: accountID, accountName, avatarUrl, created, disableCodeAccessForReviews, disableDetailedDiff, disableDraftPRComments, disableNeoSummaries, disablePRComments, ghUrls, hasContentsPermission, hasMembersPermission, id, and 5 more. Required: id, org_name.
- **Update a Pulumi integrations github enterprise by ID** (Update). Update the settings of a GitHub Enterprise Server integration in a Pulumi organization by id. Returns an empty 204 response on success. Required: id, org_name.
- **Delete a Pulumi integrations github enterprise by ID** (Delete). Delete a GitHub Enterprise Server integration from a Pulumi organization by id. Returns an empty 204 response on success. Required: id, org_name.
- **Get single Pulumi github enterprise user auth by ID** (Get). Get the GitHub Enterprise identity the current Pulumi Cloud user has linked for an organization's GitHub Enterprise integration's host. Returns: connectedAt, githubId, login. Returns 404 if the user has not linked an identity on that host. Required: id, org_name.
- **Pulumi github enterprise user auths bulk delete** (Delete). Disconnect the current Pulumi Cloud user's linked GitHub Enterprise identity for an organization's GitHub Enterprise integration's host by deleting the stored user access token and identity rows. Returns an empty 204 response on success. Idempotent — succeeds even if no identity is currently linked. Required: org_name, integration_id.
- **Get single Pulumi user auth authorize by ID** (Get). Get the GitHub Enterprise OAuth authorization URL that links the current user's identity for a Pulumi organization's GitHub Enterprise integration. Returns: authorizeUrl. Required: org_name, id.
- **List all Pulumi user auth members** (List). List the github.com logins of organization members who have linked a GitHub Enterprise identity on the given integration's host. Returns: linkedLogins. Required: org_name, integration_id.
- **List all Pulumi github access status** (List). Get the current user's GitHub OAuth access status for a Pulumi Cloud organization. Returns the access-status record with id and attributes describing the user's GitHub OAuth state. Required: org_name.
- ...and 331 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
