MCP Gateway · Claude
Connect Pulumi to Claude
Security, compliance and finance staff often need answers about cloud infrastructure without learning the Pulumi CLI. In Claude they can ask what resources exist, which ones break policy and who has access, through the Speakeasy MCP Gateway. Each person only sees the servers their role can reach.
- Category
- Infrastructure
- Tools
- 14
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Pulumi MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Pulumi call inspected and logged.
Set up
Add Pulumi to Claude in 4 steps
- 01
Add Pulumi from the catalog
An admin finds Pulumi in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Pulumi uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Pulumi
Give teams the
mcp:connectscope on the Pulumi server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Pulumi to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Pulumi from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Pulumi needs its own OAuth grant, so each person connects it once. Until they do, Pulumi calls fail while the rest of the gateway keeps working.
From then on, Pulumi's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Pulumi
Find untagged cloud resources
Ask Claude which Pulumi-managed resources are missing cost tags, grouped by project, so finance can chase the owners before the next billing review.
Summarize open security issues
Pull the open policy violations for production stacks and get a plain-language summary of each security or compliance issue for the risk register.
Review who can reach Pulumi
List the members and admins of the Pulumi organization and compare them with the current team roster during a quarterly access review.
Tools
14 tools
Each Pulumi tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
get-stacks
Call this tool to list Pulumi stacks for the authenticated user and organization. , "stacks with 'prod' in the name", "stacks created after 2024", "show me stacks containing 'bob'"). Use resource-search instead for these filtered queries.
resource-search
Search and analyze Pulumi-managed cloud resources. This tool should be used to find stacks when the user query has a filter, such as "with name 'Bob'".
get-policy-violations
Get policy violations for Pulumi stacks. Use this tool to answer questions like: - "Do I have any policy violations?" - "What security issues are in my infrastructure?" - "Show me policy violations for my production stack" - "Are there any compliance issues in my project?"
get-users
List all users (members) in the organization. Use this when asked about users, members, admins, or team members.
neo-bridge
Launch and monitor Neo tasks step by step. Pulumi Neo is a purpose-built cloud infrastructure automation agent. If the JSON result has has_more=true, call this tool again to read more data. Continue calling until has_more=false.
neo-reset-conversation
Reset the Neo conversation for a specific task
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Pulumi call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Pulumi tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Pulumi can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can compliance staff use Pulumi in Claude without deploy access?
Can Claude conversations about infrastructure be reviewed later?
How do Claude users get Pulumi?
Are Pulumi calls from Claude logged?
Connect more