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

Container UseTerraform MCP

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

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Container UseShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Developers who want coding agents isolated from the primary working tree with observable, discardable environments.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP github:dagger · 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 stars	4,075 GitHub stars · checked 2026-10-21	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Local MCP transport does not imply hosted authentication; access to container/Dagger infrastructure is deployment-defined.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	Open-source; local/remote container infrastructure and model providers may incur costs.	HCP/TFE/run costs may apply
Permissions	Agents can run code and shell operations inside provisioned environments and create git branches; host/container boundary strength depends on the runtime configuration.	HCP Terraform/TFE RBAC
Data handling	Source code, commands and logs are stored in the local/container development environment and exposed to the AI client.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	The project explicitly states it is in early development and actively evolving.	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	The project explicitly states it is in early development and actively evolving.	stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review	2026-10-21	2026-07-24
Candidate evidence	2026-10-21T00:00:00Z	2026-09-25T18:35:00Z

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

Read the evidence method →