Awslabs MCP vs MCP Cloudflare

A side-by-side look at the Awslabs MCP and MCP Cloudflare MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Awslabs MCP logoAwslabs MCPCloud Platforms · Local subprocess (stdio)AWS MCP servers for seamless integration with AWS services and resources.48FairAuth: api key requiredMCP Cloudflare logoMCP CloudflareCloud Platforms · Local subprocess (stdio)Secure MCP server for Cloudflare DNS, Transform Rules, and Page Rules59GoodAuth: api key required

Verdict: choose Awslabs MCP for cloud platforms work as a local process; choose MCP Cloudflare for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Awslabs MCP logoChoose Awslabs MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Awslabs MCP

MCP Cloudflare logoChoose MCP Cloudflare when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: CLOUDFLARE_API_TOKEN.
  • You want tools like list_zones_tool, get_zone_tool, list_dns_records_tool.
Explore MCP Cloudflare

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAwslabs MCP logoAwslabs MCPMCP Cloudflare logoMCP Cloudflare
CategoryCloud PlatformsCloud Platforms
Quality signal48/100 · Fair59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingFreeNot declared
Required env varsNone listedCLOUDFLARE_API_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars9,8210
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed34

Tools & capabilities

Awslabs MCP tools

No tool names declared yet. Check the project README from the listing page.

MCP Cloudflare tools 34

  • list_zones_toolList all Cloudflare zones accessible by the API token.
  • get_zone_toolGet Cloudflare zone details by ID or name. Provide either zone_id or zone_name, not both.
  • list_dns_records_toolList DNS records for a Cloudflare zone.
  • get_dns_record_toolGet a single DNS record by ID.
  • create_dns_record_toolCreate a new DNS record.
  • update_dns_record_toolUpdate an existing DNS record.
  • delete_dns_record_toolDelete a DNS record.
  • list_request_header_rules_toolList request header modification rules.
  • set_request_header_rules_toolSet request header modification rules (replaces all existing rules). Each rule should have: - expression: Filter expression (e.g., "true" for all requests) - description: Human-readable description - action: "rewrite" - action_parameters: {"headers": {"Header-Name": {...}}}
  • list_response_header_rules_toolList response header modification rules.
  • set_response_header_rules_toolSet response header modification rules (replaces all existing rules). Each rule should have: - expression: Filter expression (e.g., "true" for all responses) - description: Human-readable description - action: "rewrite" - action_parameters: {"headers": {"Header-Name": {...}}}
  • list_url_rewrite_rules_toolList URL rewrite rules.
  • +22 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Awslabs MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "awslabs-mcp": {
      "command": "uvx",
      "args": [
        "awslabs.aws-api-mcp-server@latest"
      ]
    }
  }
}

MCP Cloudflare

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-cloudflare": {
      "command": "uvx",
      "args": [
        "mcp-cloudflare-crunchtools"
      ],
      "env": {
        "CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Awslabs MCP is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Cloudflare belongs to Cloud Platforms and uses a local stdio subprocess. Pick Awslabs MCP for cloud platforms work and MCP Cloudflare for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Awslabs MCP is listed as free. Auth: api key required. MCP Cloudflare has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add awslabs-mcp and mcp-cloudflare as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Awslabs MCP has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 9,821 GitHub stars. MCP Cloudflare has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.