Skip to main content
Back to the Pulumi MCP server

MCP Gateway · OpenCode

Pulumi icon

Connect Pulumi to OpenCode

If you run infrastructure from the terminal, OpenCode can list your Pulumi stacks, check on Neo tasks and restart a stuck one without a trip to Pulumi Console. Speakeasy sees each prompt and tool call through the OpenCode plugin and decides whether it may run, and the plugin also records token and cost usage for every turn.

Category
Infrastructure
Tools
14
Authentication
OAuth
OpenCode
Terminal

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

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Pulumi from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Pulumi

List every stack before a cleanup

Get the full inventory of stacks in the organization, then let OpenCode compare it with the projects in your repository to find stacks nobody maintains.

get-stacks

Check on running Neo tasks

See which Pulumi Neo tasks are running, open the one about your change, and read its latest messages without switching to Pulumi Console.

neo-get-tasksneo-continue-task

Start over on a stuck Neo task

When a Neo conversation has gone in the wrong direction, reset it and send fresh instructions with the context from your terminal session.

neo-reset-conversationneo-bridge

Tools

14 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

How do I add Pulumi to OpenCode?
Copy the server's URL from its hosted install page in Speakeasy, add it to the mcp block of your OpenCode config with type set to remote, then restart OpenCode and sign in when prompted.
Does OpenCode send OpenTelemetry for Pulumi sessions?
No. OpenCode has no OpenTelemetry exporter, so session data comes through the plugin, which reports token and cost totals per turn.
How do OpenCode users get Pulumi?
An admin adds Pulumi from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Pulumi tools their access allows.
Are Pulumi calls from OpenCode 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.