Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Pulumi with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Manage cloud infrastructure via Pulumi. list stacks, track deployments, audit outputs and tag resources from any AI agent.

Included with plan

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

Complete set · 11 capabilities

The complete Pulumi capability set.

These are the exact actions your AI can choose when you ask it to work with Pulumi.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through Pulumi.

  1. 01

    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

  2. 02

    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

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

  4. 04

    Get deployment

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

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through Pulumi.

  1. 05

    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

  2. 06

    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

  3. 07

    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

  4. 08

    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

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through Pulumi.

  1. 09

    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

  2. 10

    Get organization

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

  3. 11

    Get stack

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

Observed, not estimated

898ms average. Fast in production.

Pulumi is checked daily against the live service.

Daily averagePeak 1084ms
Aug 20Today
Fastest day
756ms
Slowest day
1084ms
14-day trend
Slowing+20%

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

FAQ

Questions Pulumi owners ask.

  • 01

    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.

  • 02

    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.

  • 03

    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.

  • 04

    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.

Explore

More in Loved By Devs

Suggestions