Pulumi MCP Server
Related Servers
Alternatives to Pulumi MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language management of Cloudflare services including Workers, KV, R2, D1, Queues, and more via the Model Context Protocol.1,333 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with real-time access to live Azure infrastructure, including AKS cluster health, resource management, policy validation, and Terraform analysis through a Model Context Protocol interface.-
- AlicenseNot gradedqualityDmaintenanceExposes Salesforce development tools (scan, lint, test, deploy, verify) to AI assistants via the Model Context Protocol, enabling programmatic interaction with Salesforce projects.0MIT

infrahub-mcpofficial
AlicenseAqualityAmaintenanceEnables AI assistants to query, create, update, and propose changes to Infrahub infrastructure data through the Model Context Protocol, with branch isolation and human approval for changes.1210Apache 2.0- AlicenseDqualityDmaintenanceEnables AI assistants to interact with local Docker containers, Kubernetes clusters, and system logs using the Model Context Protocol.92 npmISC

Aribot MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables security work such as threat modeling, scanning, compliance checks, and remediation through AI assistants using the Model Context Protocol.MIT
TDQS
Scored across 5 tools
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 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.
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.
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.