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

AWS MCPTerraform 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	AWS MCPShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	AWS resource administration via unified MCP Use for AWS operational workflows requiring more than documentation lookup.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	General AWS action surface can modify cloud resources and incur cost.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	General AWS action surface can modify cloud resources and incur cost.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP AWS · 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	Not documented	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Shared repository stars	2,919 Shared repository stars (not MCP-specific) · checked 2026-10-20	Not documented
Shared-package downloads / 30 days	83,740 shared-package downloads / 30 days (not MCP-specific) · checked 2026-10-20	Not documented
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	AWS MCP Server supports OAuth and SigV4 authentication. OAuth requires AWS Sign-in permissions; SigV4 supports AWS profile-based/cross-account workflows.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	The reviewed MCP documentation does not state a separate MCP server fee. Tool calls can create, modify, or query AWS resources whose normal AWS service charges may apply.	HCP/TFE/run costs may apply
Permissions	Effective authority is controlled by AWS IAM. OAuth users need MCP authorization permissions, while service actions also require the IAM permissions for the AWS resources being accessed.	HCP Terraform/TFE RBAC
Data handling	AWS Sign-in manages OAuth consent/token refresh; OAuth access tokens are documented as valid for one hour with refresh up to 12 hours. The reviewed MCP page does not provide a separate MCP-specific data-retention/training claim.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Separate identity from AWS Documentation MCP; recommend least-privilege IAM	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	This is a broad cloud-control MCP: with sufficient IAM it can make consequential infrastructure changes and trigger billable AWS resource usage.	stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review	2026-10-19	2026-07-24
Candidate evidence	2026-10-19	2026-09-25T18:35:00Z

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

Read the evidence method →