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

AISIX MCP GatewayTerraform 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	AISIX MCP GatewayShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Organizations that want one MCP gateway to aggregate upstream servers and restrict tools per caller key Teams that need a policy boundary in front of multiple MCP servers	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Small local setups that do not need a gateway layer Production multi-tenant deployments before admin/operator controls are fully reviewed	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Admin tokens or gateway configuration are broadly accessible Caller keys are granted whole-server/all-tool access without a reason	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP reviewed-detail:aisix-mcp-gateway · 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
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	Caller requests use a gateway API key by default (Authorization: Bearer or x-api-key). Cloud management also uses admin/control-plane credentials.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	AISIX Cloud/commercial and infrastructure costs may apply; open-source deployment has hosting/operations costs.	HCP/TFE/run costs may apply
Permissions	A caller key cannot list/call tools until granted; access can be scoped to specific tools/servers/policies.	HCP Terraform/TFE RBAC
Data handling	The gateway proxies MCP requests/responses between callers and upstream MCP servers, so sensitive tool payloads traverse the gateway boundary.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Per-key tool grants are a strong least-privilege primitive A gateway becomes a central trust boundary for credentials, upstream routing, and tool availability	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	High. Central gateway compromise or misconfiguration can expose multiple upstream tools/credentials. Review admin-token handling, tenant separation, audit logging, rate limits, and emergency revocation.	stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review	2026-09-11	2026-07-24
Candidate evidence	2026-09-11T00:00:00.000Z	2026-09-25T18:35:00Z

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

Read the evidence method →