Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldpulumiMCP100 RecommendedTerraform MCPMCP100 Recommended
Task fit
Best for
  • Infrastructure discovery and policy-aware Pulumi operations across stacks and cloud resources.
  • Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for
  • Teams outside the publisher ecosystem or without least-privilege credentials
  • Users who need a fully reviewed MCP100 recommendation today
Avoid when
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

First-party MCP

ecosystem:pulumi · Publisher source ↗

First-party MCP

HashiCorp · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

1,534

GitHub stars · checked 2026-09-25T18:35:00Z

Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe canonical recommended user path is the hosted https://mcp.ai.pulumi.com/mcp service and its documented Pulumi OAuth flow. Do not use local package or repository credentials as an identity or popularity substitute for this hosted profile.HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
CostThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.HCP/TFE/run costs may apply
PermissionsPulumi organization and stack permissions govern the resources exposed; tool selection can limit the enabled surface.HCP Terraform/TFE RBAC
Data handlingAuthorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive cloud & devops information.registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs
  • Delegated infrastructure execution can create cost and production impact, so mutation tools need explicit review.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk contextDelegated infrastructure execution can create cost and production impact, so mutation tools need explicit review. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review2026-07-302026-07-24
Candidate evidence2026-09-24T04:25:05.554391Z2026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →