Pulumi MCP Server
README.md
# Pulumi 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](https://github.com/pulumi/mcp-server/issues) if you encounter bugs or need support for additional Pulumi commands.
A server implementing the [Model Context Protocol](https://modelcontextprotocol.io) (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.
## Usage
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:
```json
{
"mcpServers": {
"pulumi": {
"command": "npx",
"args": ["@pulumi/mcp-server"]
}
}
}
```
## Available Commands
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.
* **`getResource`**: 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').
* **`listResources`**: 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').
## Development
1. Clone the repository.
2. Install dependencies: `npm install`
3. Build the project: `npm run build`
## License
This project is licensed under the Apache-2.0 License. See the [LICENSE](LICENSE) file for details. TDQS
D1.8/5.0
Scored across 5 tools
Disambiguation5/5
Tool names clearly distinguish registry operations (get/list resources) from CLI operations (preview, up, stack-output). Each name implies a distinct action, reducing ambiguity.
Naming Consistency2/5
Naming style is inconsistent: 'getResource' and 'listResources' use camelCase, 'preview' and 'up' are lowercase single words, and 'stack-output' uses hyphen. No uniform verb_noun pattern.
Tool Count5/5
With 5 tools, the set is well-scoped for a Pulumi MCP server covering registry and CLI basics. Each tool serves a distinct purpose without unnecessary duplication.
Completeness2/5
The tool set lacks essential Pulumi operations like stack create/destroy, config management, and resource update. The domain is only partially covered, leading to potential dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues