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.
| Evidence field | Terraform MCPMCP100 Recommended | Cloudflare MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP HashiCorp · Publisher source ↗ | First-party MCP Cloudflare · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Not documented | Repo: Sep 17, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 1,534 GitHub stars · checked 2026-09-25T18:35:00Z | 880 GitHub stars · checked 2026-09-24T04:14:26.352000Z |
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN | Cloudflare's managed broad MCP endpoint is https://mcp.cloudflare.com/mcp and uses Cloudflare OAuth with Streamable HTTP. The older cloudflare/mcp-server-cloudflare family is domain-specific and is not this profile's canonical identity. |
| Cost | HCP/TFE/run costs may apply | Cloudflare does not document a separate fee for connecting to its managed MCP endpoints. Charges and limits for underlying Cloudflare products, the user's Cloudflare plan, and the AI client still apply. |
| Permissions | HCP Terraform/TFE RBAC | The Cloudflare API MCP server can search the typed Cloudflare API and execute calls across the authorized account. OAuth redirects the user to Cloudflare to select permissions. Product-specific servers expose narrower capabilities such as audit logs, DNS analytics, AI Gateway logs, GraphQL analytics, or documentation search. |
| Data handling | registry/HCP/TFE data may reach connected MCP client/LLM | Tool requests are processed by Cloudflare's hosted MCP service. For the API server, generated JavaScript runs in an isolated Dynamic Worker sandbox and can read or modify data reachable through the granted Cloudflare API permissions. Product-specific servers may return logs, prompts and responses, configuration, analytics, documents, or security findings to the MCP client. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default | The two-tool search/execute design can reach a very broad API surface. Prefer a product-specific endpoint where possible, grant minimum OAuth permissions, require confirmation for execute operations, inspect audit logs, and separate untrusted content from administrative actions. This review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-24 |
| Candidate evidence | 2026-09-25T18:35:00Z | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →