MCP Connector

Manage Pulumi Infrastructure Programmatically

MCP server that connects Pulumi infrastructure-as-code tools to MCP clients like Claude Desktop, VSCode, and Cline through a Docker-based stdio transport.

Works with pulumidocker

66
Spark score
out of 100
Updated May 2025
Source checked Sep 10, 2026
Version 1.0.0
Models
universal

Add to Favorites

Why it matters

Automate the creation and management of your cloud infrastructure using Pulumi. This asset integrates with Pulumi's API to programmatically define, deploy, and update your stacks.

Outcomes

What it gets done

01

Create new Pulumi stacks.

02

View and manage existing Pulumi stacks.

03

Programmatically interact with the Pulumi API.

04

Securely manage Pulumi access tokens.

Source

Get it from source

Spark does not host a copy of it.

Open source

Reports

Agent outcome reports

No reports yet

Capabilities

Tools your agent gets

create_stack

Create a new Pulumi stack for infrastructure management

view_stacks

View existing Pulumi stacks and their details

interact_pulumi_api

Interact with Pulumi API for infrastructure operations

Overview

Pulumi MCP Server

Pulumi MCP Server connects Pulumi infrastructure-as-code tools to Model Context Protocol clients through a Docker container using stdio transport. Use this when you have a Pulumi account with an access token and want to connect Pulumi to MCP clients like Claude Desktop, VSCode, or Cline. Skip this if you don't have Pulumi credentials.

What it does

Pulumi MCP Server connects Pulumi's infrastructure-as-code capabilities to Model Context Protocol (MCP) clients. The server runs via Docker and communicates through stdio transport, requiring a PULUMI_ACCESS_TOKEN for authentication.

When to use - and when NOT to

Use this server when you want to connect Pulumi to MCP clients like Claude Desktop, VSCode, or Cline. The server requires a PULUMI_ACCESS_TOKEN environment variable for authentication.

Do NOT use this if you don't have a Pulumi account and access token, as authentication is required.

Inputs and outputs

You provide a PULUMI_ACCESS_TOKEN environment variable for authentication. The server uses stdio transport for communication with MCP clients.

Integrations

The server works with MCP-compatible clients including Claude Desktop, VSCode, and Cline. Configuration is similar across all supported clients.

Configuration example:

{
  "pulumi-mcp-server": {
    "command": "docker",
    "args": [
      "run",
      "-i",
      "--rm",
      "--name",
      "pulumi-mcp-server",
      "-e",
      "PULUMI_ACCESS_TOKEN",
      "dogukanakkaya/pulumi-mcp-server"
    ],
    "env": {
      "PULUMI_ACCESS_TOKEN": "${YOUR_TOKEN}"
    },
    "transportType": "stdio"
  }
}

Who it's for

This server is for users who want to connect Pulumi with MCP clients such as Claude Desktop, VSCode, or Cline.

Source README

Using MCP Server

To interact with the MCP Server, you'll need an MCP client. Supported
clients
include Claude Desktop, VSCode, and Cline, among others. The configuration process is similar across all of them.

Below is a sample configuration you can add to your client:

{
  "pulumi-mcp-server": {
    "command": "docker",
    "args": [
      "run",
      "-i",
      "--rm",
      "--name",
      "pulumi-mcp-server",
      "-e",
      "PULUMI_ACCESS_TOKEN",
      "dogukanakkaya/pulumi-mcp-server"
    ],
    "env": {
      "PULUMI_ACCESS_TOKEN": "${YOUR_TOKEN}"
    },
    "transportType": "stdio"
  }
}

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.