Skip to main content
Back to the MCP Gateway catalog

MCP Gateway · Catalog

Pulumi MCP Server icon

Pulumi MCP server

Official

Pulumi MCP is the official Model Context Protocol server for Pulumi, with OAuth and tools that let agents inspect stacks, search resources, review policy violations, and run deployments. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Category
Infrastructure
Tools
14
Authentication
OAuth
Connects through
Speakeasy MCP Gateway

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.

Deploy on MCP Gateway

Connect from your AI client

Use Pulumi in the clients your teams already use

Setup steps and the controls Speakeasy applies, for each client.

Tools

14 tools

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

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.

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

neo-continue-task

Continue or return to an existing Neo task. Use this to resume work on a previous task, check its status, or see what happened. , "the task about Pulumi ESC"). This command will poll the task and return any new messages.

neo-get-tasks

List Neo tasks for the organization. Returns task names, IDs, statuses, and links to view them in Pulumi Console.

get-type

Get the JSON schema for a specific JSON schema type reference

get-resource

Returns information about a Pulumi Registry resource

get-function

Returns information about a Pulumi Registry function

list-resources

List all resource types for a given provider and module

list-functions

List all function types for a given provider and module

deploy-to-aws

Deploy application code to AWS by generating Pulumi infrastructure. This tool automatically analyzes your application files and provisions the appropriate AWS resources (S3, Lambda, EC2, etc.) based on what it finds. No prior analysis needed - just invoke directly.

Questions

Frequently asked questions

What is a Pulumi MCP server?
A Pulumi MCP server exposes Pulumi to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as get-stacks or resource-search to work with Pulumi. The server in this catalog is the official Pulumi MCP server, which authenticates with OAuth.
What can you do with Pulumi MCP?
Agents can inspect stacks, search resources, review policy violations, and run deployments. The catalog lists 14 tools for this server, including get-stacks, resource-search, and get-policy-violations. The full list with descriptions is on this page.
Why put Pulumi MCP behind an MCP gateway?
Connecting the Pulumi MCP server directly to each client means a separate credential per developer, no inventory of who can reach Pulumi through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Pulumi server, so sign-in runs through your identity provider, role-based access decides which teams can call which Pulumi tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Pulumi and to every other server in your catalog.
How do you connect Pulumi MCP through a gateway?
Add the Pulumi server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Pulumi tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Pulumi MCP?
Community-built Pulumi MCP servers wrap the same Pulumi surface but are not vendor-maintained, and most authenticate with a static credential that gives an agent everything the credential owner can touch. This catalog lists the official Pulumi MCP server, which uses OAuth. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access, and an audit trail of every call.

AI everywhere.

Control here.