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 | AWS Infrastructure as Code MCP ServerWatchlist candidate | Cloudflare MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP github:awslabs · Publisher source ↗ | First-party MCP Cloudflare · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Stale Repo: Not documented Package: Not documented | Repo: Aug 11, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 4,074 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| Client coverage | ||
| Client coverage details | Not documented | 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 | Uses AWS credentials only for AWS API-backed troubleshooting; local validation/documentation functions do not require AWS permissions. | Cloudflare's managed remote MCP servers use Cloudflare OAuth. The current API endpoint is https://mcp.cloudflare.com/mcp and supports Streamable HTTP; the older SSE transport is deprecated. |
| Cost | Server is open source; AWS account/service and model-provider usage may incur costs. | 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 | Publisher 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. | 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 | AWS API responses used for troubleshooting can be shared with the connected third-party AI provider; AWS explicitly calls this out in its privacy notice. | 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 | The canonical identity is the broader AWS IaC MCP Server, not “AWS CDK”; Selected promotion should evaluate this exact server and its MCP-specific adoption as a whole. | 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-09-13T00:00:00Z | 2026-07-24 |
| Candidate evidence | 2026-09-13T00:00:00Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →