Skip to main content
Back to the Pulumi MCP server

MCP Gateway · Claude Cowork

Pulumi icon

Connect Pulumi to Claude Cowork

A full infrastructure review touches every stack, every policy and every member, which is too much for one chat turn. Cowork can run it as a longer task: gather the Pulumi data, cross-check it and write the findings up. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties the session to a person.

Category
Infrastructure
Tools
14
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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

Set up

Add Pulumi to Claude Cowork in 4 steps

  1. 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.

  2. 02

    Choose who can use Pulumi

    Give teams the mcp:connect scope on the Pulumi server through team access or a role. Claude Cowork connects to the Pulumi server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Pulumi from Claude Cowork

    The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Pulumi

Write a quarterly infrastructure review

Cowork lists every stack, searches each for its resources, and drafts a review document that shows what changed, what looks unused and which projects grew fastest.

get-stacksresource-search

Turn policy violations into a remediation plan

Gather open violations across the organization, group them by project and severity, and produce a plan that names an owner for each group from the member list.

get-policy-violationsget-users

Follow a Neo task to the end

Launch a Pulumi Neo task for a routine change and keep reading its progress until it finishes, then summarize what Neo did for the change record.

neo-bridgeneo-continue-task

Tools

14 tools

Each Pulumi tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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.

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

See all 14 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Does the device agent manage Pulumi access in Cowork?
No. Neither the device agent nor MDM reaches Cowork, so the Claude-side plugin setup always applies. Personal Claude accounts can't be governed in Cowork.
Can Cowork run Pulumi deployments?
Only if the person's role allows tools such as deploy-to-aws or neo-bridge. Each of the 14 Pulumi tools can be allowed or denied per team and role at the MCP Gateway.
How do Claude Cowork users get Pulumi?
An admin adds Pulumi from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Pulumi tools their access allows.
Are Pulumi calls from Claude Cowork logged?
Yes. Pulumi calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Pulumi in other clients

AI everywhere.

Control here.