Skip to main content
Back to the Pulumi MCP server

MCP Gateway · Cursor

Pulumi icon

Connect Pulumi to Cursor

In Cursor, the Pulumi program is open in the editor while the agent checks the registry and the live estate. It can confirm a provider function's signature, inspect a stack's resources and list who in the organization owns what. Every Cursor hook event carries the developer's email, so each Pulumi call is attributed.

Category
Infrastructure
Tools
14
Authentication
OAuth
Cursor
Editor and 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 Cursor 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. 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.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Pulumi from Cursor

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

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Pulumi

Get a provider function right

When you call a lookup such as an AMI or VPC query, Cursor lists the module's function types and reads the one you need, so the arguments match the registry.

list-functionsget-function

Inspect resources behind a failing stack

Search the resources in the stack you are editing by type or name, compare them with the code on screen, and spot what drifted.

resource-searchget-stacks

Find who to ask about a stack

List the members and admins of the Pulumi organization so you know who to tag on a pull request that changes shared infrastructure.

get-users

Tools

14 tools

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

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

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Can Speakeasy block a Pulumi deploy from Cursor?
Yes. Cursor hooks send each tool call to Speakeasy, which allows or denies it before Cursor runs it, and they fail closed. Tools such as deploy-to-aws can also be denied per team and role at the MCP Gateway.
Do Pulumi hooks run in Cursor Cloud agents?
Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
How do Cursor users get Pulumi?
An admin adds Pulumi from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Pulumi tools their access allows.
Are Pulumi calls from Cursor 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.