mcp-server

Note: This MCP server is currently under active development. Its API (including available commands and their arguments) is experimental and may introduce breaking changes without notice. Please file an issue on GitHub if you encounter bugs or need support for additional Pulumi commands.

A server implementing the Model Context Protocol (MCP) for interacting with Pulumi CLI using the Pulumi Automation API and Pulumi Cloud API.

This package allows MCP clients to perform Pulumi operations like retrieving package information, previewing changes, deploying updates, and retrieving stack outputs programmatically without needing the Pulumi CLI installed directly in the client environment.

The Pulumi CLI has to be installed on you machine.

This package is primarily intended to be integrated into applications that can use MCP servers as AI tools. For example, here is how you can include Pulumi MCP Server in Claude desktop's MCP configuration file:

{
  "mcpServers": {
    "pulumi": {
      "command": "npx",
      "args": ["@pulumi/mcp-server@latest"]
    }
  }
}

You can also run the Pulumi MCP Server as a Docker container. This approach eliminates the need to install Node.js and the package dependencies directly on your host machine.

To build the container:

docker build -t pulumi/mcp-server:latest .

To use the containerized server with MCP clients, you'll need to configure the client to use the Docker container. For example, in Claude desktop's MCP configuration:

{
  "mcpServers": {
    "pulumi": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "pulumi/mcp-server:latest"]
    }
  }
}

For Pulumi operations that require access to local Pulumi projects, you'll need to mount the appropriate directories. For example, if your Pulumi project is in ~/projects/my-pulumi-app:

{
  "mcpServers": {
    "pulumi": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-v", "~/projects/my-pulumi-app:/app/project", "pulumi/mcp-server:latest"]
    }
  }
}

Then when using the MCP tools, you would reference the project directory as /app/project in your requests.

The server exposes handlers for the following Pulumi operations, callable via MCP requests:

• preview: Runs pulumi preview on a specified stack.
  • workDir (string, required): The working directory containing the Pulumi.yaml project file.
  • stackName (string, optional): The stack name to operate on (defaults to 'dev').
• up: Runs pulumi up to deploy changes for a specified stack.
  • workDir (string, required): The working directory containing the Pulumi.yaml project file.
  • stackName (string, optional): The stack name to operate on (defaults to 'dev').
• stack-output: Retrieves outputs from a specified stack after a successful deployment.
  • workDir (string, required): The working directory containing the Pulumi.yaml project file.
  • stackName (string, optional): The stack name to retrieve outputs from (defaults to 'dev').
  • outputName (string, optional): The specific stack output name to retrieve. If omitted, all outputs for the stack are returned.
• get-resource: Returns information about a specific Pulumi Registry resource, including its inputs and outputs.
  • provider (string, required): The cloud provider (e.g., 'aws', 'azure', 'gcp', 'random') or github.com/org/repo for Git-hosted components.
  • module (string, optional): The module to query (e.g., 's3', 'ec2', 'lambda').
  • resource (string, required): The resource type name (e.g., 'Bucket', 'Function', 'Instance').
• list-resources: Lists available resources within a Pulumi provider package, optionally filtered by module.
  • provider (string, required): The cloud provider (e.g., 'aws', 'azure', 'gcp', 'random') or github.com/org/repo for Git-hosted components.
  • module (string, optional): The module to filter by (e.g., 's3', 'ec2', 'lambda').

1. Clone the repository.
2. Install dependencies: make ensure
3. Build the project: make build
4. Test the project: make test

This project is licensed under the Apache-2.0 License. See the LICENSE file for details.