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

Kong Konnect 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	Kong Konnect MCPShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Konnect gateway configuration and operational diagnostics Use when the organization manages gateway infrastructure in Kong Konnect.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Dynamic API execution broadens the effective permission surface beyond the three visible tools.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Dynamic API execution broadens the effective permission surface beyond the three visible tools.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP Kong · 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	6 Shared repository stars (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	Browser-based authentication, Personal Access Token (PAT), or System Account Access Token (SPAT) for automated workflows.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	No separate Konnect MCP fee was documented in the reviewed MCP page. Underlying Kong/Konnect products and gateways have paid plans and usage-based charges depending on deployment and features.	HCP/TFE/run costs may apply
Permissions	Every MCP query respects Konnect RBAC and regional data boundaries associated with the authenticated user, PAT, or SPAT. Tool access follows the user's permission level.	HCP Terraform/TFE RBAC
Data handling	Kong states that no user data is sent to LLM providers through the MCP server unless KAi is enabled. When KAi is enabled, its KnowledgeBase tool creates embeddings from queries; Kong states those queries are not used to train models.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Use regional endpoint / minimal RBAC; static tool count is 3 but execute is broad	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	The small visible tool set includes dynamic API execution, so the effective action surface can be much broader than the MCP tool count and can modify gateway configuration within the authenticated RBAC scope.	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 →