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 fieldAWS Infrastructure as Code MCP ServerShortlist candidateTerraform MCPMCP100 Recommended
Task fit
Best for
  • AWS IaC developers who want official CloudFormation diagnostics and CDK/CloudFormation knowledge inside an MCP client.
  • 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:awslabs · 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

Package downloads / 30 days

103,803

package downloads / 30 days · checked 2026-10-21

No reliable download data
Shared repository stars

9,806

Shared repository stars (not MCP-specific) · checked 2026-10-21

Not documented
Client coverage
Client coverage detailsNot documented
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
AuthenticationUses AWS credentials only for AWS API-backed troubleshooting; local validation/documentation functions do not require AWS permissions.HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
CostServer is open source; AWS account/service and model-provider usage may incur costs.HCP/TFE/run costs may apply
PermissionsPublisher documents read permissions such as `cloudformation:Describe*` and `cloudtrail:LookupEvents` for troubleshooting. The reviewed server evidence does not justify describing CDK deployment mutation as a core capability.HCP Terraform/TFE RBAC
Data handlingAWS API responses used for troubleshooting can be shared with the connected third-party AI provider; AWS explicitly calls this out in its privacy notice.registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs
  • The canonical identity is the broader AWS IaC MCP Server, not “AWS CDK”; Recommended promotion should evaluate this exact server and its MCP-specific adoption as a whole.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk contextThe canonical identity is the broader AWS IaC MCP Server, not “AWS CDK”; Recommended promotion should evaluate this exact server and its MCP-specific adoption as a whole.stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review2026-10-212026-07-24
Candidate evidence2026-10-21T00:00:00Z2026-09-25T18:35:00Z

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

Read the evidence method →