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.
- Connects with an API key
- Free 14-day trial
- No credit card
List every project in our platform Pulumi organization
Working in Pulumi with Elaichi
-
List all Pulumi agents signups
-
Get single Pulumi signup validate by ID
-
List all Pulumi claim status
How to connect Pulumi to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Pulumi MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Pulumi MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Pulumi through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Pulumi is logged.
-
Platform engineering
Find the right project before anyone touches it
Ask which Pulumi organizations and projects exist and get the list back in chat. Pick the right one before an apply ever starts.
-
DevOps
Start a Pulumi apply from chat
Kick off an apply for a project without opening a terminal. The audit log records who started it and when.
-
Security
Put a change gate in front of production
Create or update a Pulumi change gate so a risky change waits for review, then remove it once the window closes.
-
Release management
Check which CLI versions teams are running
Pull the list of Pulumi CLI versions ahead of a rollout so you know who is behind before it matters.
-
Engineering
Link Azure DevOps or Bitbucket to Pulumi
Set up or review the connection between a Pulumi organization and Azure DevOps or Bitbucket, and check access status when a pipeline stalls.
-
IT
Onboard a new Pulumi agent without passing keys
Create a Pulumi agent signup, submit the claim and check its status, all from the same chat and without handing anyone a credential.
Try asking
- “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?”
What connecting Pulumi gets you
6 screens from Elaichi, each doing one job for your Pulumi account.
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Pulumi, get a live answer.
Projects, change gates and applies answered in plain language from Pulumi as it is now.
Copy the endpoint
AI apps
One endpoint puts Pulumi in every client.
Claude, ChatGPT and Cursor reach Pulumi through one governed endpoint, no SDK, no shared API key.
Tool catalog
381 Pulumi tools, no code to write.
Organizations, projects, change gates, applies and CLI versions, cataloged and ready to call.
Toolboxes
Every team gets its own Pulumi toolbox.
Security keeps change gates, DevOps keeps applies, each team sees only what it needs.
Shared connections
Share Pulumi access, never the API key.
One person connects Pulumi, teammates work through it, and nobody else sees a credential.
Audit log
Every Pulumi call has a name on it.
Who started the apply, who edited the change gate, when, all in one append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Pulumi digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Pulumi
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Pulumi
Queued
Workflows
A schedule starts the apply, you approve.
Pulumi projects are fetched, grouped and drafted into a digest, then posted after a person signs off.
Pulumi health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Change gates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Platform 34%
Production 27%
Staging 21%
Security 18%
Collections and dashboards
Pulumi health, computed, not asked for.
Projects, change gates and applies counted on a schedule, by team, with no model in the math.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Pulumi tools for your AI agents
381 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pulumi, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 206 of 381 Pulumi tools here. Connect Pulumi and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
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 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.
Put Pulumi in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot