2,500+ MCP servers ready to use
Vinkius

Pulumi MCP Server for Cursor 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Pulumi and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "pulumi": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Pulumi
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Pulumi MCP Server

Connect your Pulumi account to any AI agent and take full control of your infrastructure-as-code through natural conversation.

Cursor's Agent mode turns Pulumi into an in-editor superpower. Ask Cursor to generate code using live data from Pulumi and it fetches, processes, and writes — all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Organization Discovery — List organizations and retrieve their details, team settings and member info
  • Stack Management — List, create and delete stacks (infrastructure environments) across all your projects
  • Deployment Tracking — Monitor stack update history with status (succeeded, failed, in-progress), resource changes and error logs
  • Output Inspection — View exported output values from the latest deployment (URLs, IPs, resource IDs)
  • Tag Management — List and set custom tags on stacks for organization and filtering (environment, team, cost-center)

The Pulumi MCP Server exposes 11 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Pulumi to Cursor via MCP

Follow these steps to integrate the Pulumi MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Pulumi

Open Agent mode in chat and ask: "Using Pulumi, help me..."11 tools available

Why Use Cursor with the Pulumi MCP Server

Cursor AI Code Editor provides unique advantages when paired with Pulumi through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Pulumi + Cursor Use Cases

Practical scenarios where Cursor combined with the Pulumi MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Pulumi MCP Tools for Cursor (11)

These 11 tools become available when you connect Pulumi to Cursor via MCP:

01

create_stack

A stack is an isolated, independently configurable instance of your Pulumi program. Requires the org name, project name and stack name (e.g. "staging", "prod"). Returns the created stack with its URL. Create a new Pulumi stack

02

delete_stack

The stack must be empty (no resources) or force deletion must be enabled. Provide the org name, project name and stack name. WARNING: this action is irreversible. Delete a Pulumi stack

03

get_current_user

Returns the user's GitHub login, avatar URL, email and name. Use this to verify your access token is working correctly and to see which identity the API calls will appear as. Get the currently authenticated Pulumi user

04

get_deployment

Provide the org name, project name, stack name and deployment version number. Get details for a specific Pulumi deployment

05

get_organization

Provide the organization name (slug). Get details for a specific Pulumi organization

06

get_stack

Provide the org name, project name and stack name. Get details for a specific Pulumi stack

07

get_stack_outputs

Outputs are values your Pulumi program exports, such as URLs, IP addresses, resource IDs and connection strings. Useful for discovering endpoint addresses and configuration values after infrastructure deployment. Get the exported output values from a Pulumi stack

08

list_deployments

Each deployment shows its version number, status (succeeded, failed, in-progress), start/end time, resource changes (created, updated, deleted) and the user who triggered it. Use this to audit infrastructure changes and track deployment success/failure patterns. List deployment history for a Pulumi stack

09

list_stack_tags

Tags are key-value metadata labels used for organizing, filtering and managing stacks (e.g. environment=prod, team=platform, cost-center=engineering). List tags on a Pulumi stack

10

list_stacks

Each stack represents an isolated, independently configurable instance of your infrastructure (e.g. dev, staging, prod). Returns stack name, project name, last update info, resource count and whether updates are in progress. List all stacks in a Pulumi organization

11

set_stack_tag

Tags are used for organizing, filtering and managing stacks (e.g. key="environment", value="prod", key="team", value="platform"). Provide the org name, project name, stack name, tag name and tag value. Set a tag on a Pulumi stack

Example Prompts for Pulumi in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Pulumi immediately.

01

"Show me all stacks in my organization."

02

"What was the result of the latest deployment to my-infra/prod?"

03

"Show me the exported outputs from the prod stack."

Troubleshooting Pulumi MCP Server with Cursor

Common issues when connecting Pulumi to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Pulumi + Cursor FAQ

Common questions about integrating Pulumi MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design — tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Pulumi to Cursor

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.