An astronaut overseeing a futuristic data hub

Connect Pulumi to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run cloud operations through your AI agent without opening the console.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 11 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through Pulumi.

  1. 01

    Create stack

    Creates a new Pulumi stack for a specific organization and project. It returns the new stack's URL once it is ready.

  2. 02

    Get stack outputs

    Retrieves exported values like URLs, IP addresses, or connection strings from a specific stack. This is how you find your deployment endpoints.

  3. 03

    List deployments

    Shows the history of stack updates, including status, resource changes, and who triggered the deployment. Use this to audit your infrastructure changes.

  4. 04

    List stack tags

    Lists all metadata tags currently applied to a stack. This helps you see how stacks are organized by team or environment.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through Pulumi.

  1. 05

    List stacks

    Returns a list of all stacks within a Pulumi organization, including their current status and resource counts.

  2. 06

    Set stack tag

    Applies a custom key-value tag to a stack. You can use this to label stacks for cost centers or environment tracking.

  3. 07

    Get current user

    Identifies the currently authenticated Pulumi user. It provides your GitHub login and email to confirm your identity.

  4. 08

    Get organization

    Fetches detailed information about a specific Pulumi organization using its slug.

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through Pulumi.

  1. 09

    Delete stack

    Permanently removes a stack from your organization. This action is irreversible and requires the stack to be empty.

  2. 10

    Get deployment

    Provides specific details about a single deployment version within a stack.

  3. 11

    Get stack

    Retrieves the full details for a specific Pulumi stack.

Real work

What teams actually run

01

Post-Deployment Verification

After a run, ask your agent for the new API endpoint or database connection string.

02

Deployment Troubleshooting

Ask your agent why a specific deployment failed by reviewing the error logs and resource changes.

03

Resource Organization

Use the agent to apply tags to stacks to keep your environments organized by team or cost center.

04

Infrastructure Auditing

Quickly list all stacks in an organization to get a high-level view of your current footprint.

Automate a task

Put Pulumi to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Pulumi works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Pulumi to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

893ms average. Fast in production.

Pulumi is checked daily against the live service.

Daily averagePeak 1172ms
Oct 3Today
Fastest day
760ms
Slowest day
1172ms
14-day trend
Slowing+22%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 11 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Pulumi, so you can see the experience inside your AI.

It does not authenticate your account with Pulumi. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Pulumi Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_v2N5nlYKKcBMg7t6tvswP5zOuY1KsfB14QgLHciO/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Pulumi capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "pulumi-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_v2N5nlYKKcBMg7t6tvswP5zOuY1KsfB14QgLHciO/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Pulumi in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Pulumi owners hand off.

This MCP is built for technical teams who manage cloud resources through code and want to interact with their infrastructure via chat.

  • 01

    DevOps Engineers

    They use the agent to check deployment statuses and inspect outputs without leaving their terminal or IDE.

  • 02

    Platform Teams

    They use the agent to audit changes and manage organization-wide stack tags.

  • 03

    Developers

    They use the agent to find resource endpoints and verify that their infrastructure provisioned correctly.

FAQ

Questions Pulumi owners ask.

  • 01

    How do I connect my Pulumi account?

    You subscribe to the MCP on Vinkius and enter your Pulumi Access Token. Once connected, your AI client can immediately start interacting with your Pulumi organization.

  • 02

    Which AI clients can I use with this MCP?

    You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 03

    Can I delete stacks using my AI agent?

    Yes, you can use the delete_stack capability. Note that the stack must be empty or you must enable force deletion, and this action cannot be undone.

  • 04

    What kind of information can the agent retrieve from my stacks?

    The agent can retrieve stack details, deployment history, resource counts, and exported outputs like IP addresses and URLs.

  • 05

    Is my Pulumi token stored securely?

    Vinkius manages your credentials and keeps the connection running so you don't have to handle manual configuration every time you start a session.

  • 06

    How do I get a Pulumi Access Token?

    Log in to the Pulumi Console, go to Account Settings > Access Tokens, click Create Token, give it a name and copy the token immediately. it starts with pul_ and won't be shown again.

  • 07

    What is a Pulumi stack?

    A stack is an isolated, independently configurable instance of your Pulumi program. Stacks typically represent different environments like dev, staging and prod. Each stack has its own configuration, state, outputs and deployment history. Use list_stacks to discover all stacks in an organization.

  • 08

    Can I see the deployment history of a stack?

    Yes! Use list_deployments with the org name, project name and stack name. It returns the update history showing version number, status (succeeded, failed, in-progress), start/end time and resource change counts. Use get_deployment with a specific version for detailed logs and error messages.

  • 09

    Can I view the outputs of a stack?

    Yes! Use get_stack_outputs with the org name, project name and stack name. It returns all exported output values from the latest successful deployment, such as URLs, IP addresses, resource IDs and connection strings. This is useful for discovering endpoint addresses after infrastructure deployment.

Connect Pulumi to Claude, Cursor, ChatGPT & more