# Cloudflare Claude Code MCP Evaluation

**Category:** Cloud Hosting
**Score:** 16 (D)

This is the agent-readable Devtool Arena evaluation page for Cloudflare on Claude Code MCP.

## Summary

| Metric | Value |
|--------|-------|
| Status | completed |
| Overall score | 16 |
| Grade | D |
| Eval score | 7 |
| Discovery score | 38 |
| Cost | $0.23 |
| Runtime | 3m 51s |
| Tool calls | 18 |
| Errors | 3 |
| Tokens used | 415862 |
| Success | No |

## Agent-Readiness Checklist

| Signal | Evidence |
|--------|----------|
| Context7 | Not found |
| llms.txt | Not found |
| MCP server | Not found |
| Typed SDK | Not found |
| OpenAPI | Not found |
| Agent skills | Not found |
| CLI | Not found |

## Evaluation Prompt

````text

# Task
Using the Cloudflare MCP, manage hosting resources:

1. Discover available MCP tools and their capabilities
2. List existing sites/projects/services/apps
3. Get details for one of the existing sites or create a new one
4. Check deployment status or recent deployments
5. Print all output clearly labeled for each step

Use ONLY the MCP tools for all operations.

You MUST use the Cloudflare MCP server to accomplish this task.
Use the MCP tools for the actual product operations. Do NOT use curl, fetch, raw HTTP requests, CLI commands, or SDK calls as substitutes.

Use the MCP tools' help/descriptions to understand what each tool does.
If you need additional context, check the documentation: https://developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/

## Setup
Do NOT assume the Cloudflare MCP server is already installed or already running in this sandbox.
Review the installation and authentication details below before starting the task.

### Installation
Transport: `http`
This MCP server uses `http` transport.
Claude Code should connect to: `https://mcp.cloudflare.com/mcp`
Do not assume a local MCP package is already installed; the task depends on the remote server being reachable.
Bootstrap notes: Verified against Cloudflare's own docs (developers.cloudflare.com/agents/model-context-protocol/mcp-servers-for-cloudflare/): the server is remote, Streamable HTTP at https://mcp.cloudflare.com/mcp (the deprecated /sse alias also still works but should not be used for new connections). Primary auth is interactive OAuth with dynamic client registration + authorization-code flow (matches stored_auth_method 'oauth_rs_dcr_authcode') — Claude Code opens a browser redirect to Cloudflare the first time the server is used, no env vars are needed for this path, consistent with stored_auth_env_vars: []. Docs also describe a non-interactive alternative for CI/automation: create a Cloudflare API token and send it as 'Authorization: Bearer <token>' header rather than a named env var. If this sandbox cannot complete an interactive OAuth browser flow, the scored run will need that fallback — e.g. `claude mcp add --transport http cloudflare-api https://mcp.cloudflare.com/mcp --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"` — in which case CLOUDFLARE_API_TOKEN should be treated as required. I did not set bearer_token_env_var/required_env_vars for this because the vendor doc presents OAuth as the default/primary path and gives no fixed env-var name for the token.

### Authentication
Authentication method: `oauth_rs_dcr_authcode`
No MCP auth environment variables were provided. Use the documentation if the server reports authentication errors.

## Execution
1. The harness has already written the launch configuration for `cloudflare`. Start with the task directly; do not rewrite agent settings, `.mcp-runtime.json`, or build a separate MCP client unless the connected server still fails after a normal retry.
2. You do not need to enumerate every MCP tool up front; inspect only the relevant tools you need. Agent-facing MCP tool names may be namespaced like `mcp__cloudflare__<tool_name>`.
3. Complete the task described above using MCP tools for the actual product operations.
4. If the server fails to start or authenticate, debug the documented setup and retry. Do not fall back to raw HTTP, SDK, CLI, or manual JSON-RPC/MCP calls as a substitute for exposed MCP tools.

Work in the /home/daytona/app directory.
If you use Bash during setup or debugging, limit it to installation/configuration work and then return to MCP tools for the task itself.
If there are errors, debug and fix them until the task runs successfully.

## Summary
When you are done, write a JSON summary file to /home/daytona/app/results.json with this structure:
{
  "operations": [
    {"step": 1, "description": "What you did", "mcp_tool": "tool_name", "success": true/false, "output_summary": "brief result"},
    ...
  ],
  "overall_success": true/false,
  "notes": ["any relevant notes about the execution"]
}

````

## Grader Results

| Check | Passed | Weight | Score | Details |
|-------|--------|--------|-------|---------|
| Task | No | — | — | — |
| Llms Txt | Yes | — | 10 | — |
| Tool Count | No | — | 0 | — |
| Auth Method | Yes | — | 8 | — |
| Official Mcp | Yes | — | 5 | — |
| Output Schema | No | — | 0 | — |
| Tool Stability | Yes | — | 5 | — |
| Tool Description Length | Yes | — | 10 | — |

## Run Artifacts

| Artifact | Value |
|----------|-------|
| Conversation turns | 21 |
| Tool call traces | 18 |
| Generated files | 1 |
| Exit code | — |
| Completed at | 2026-10-04T16:33:00.439611+00:00 |

### Generated Files

- /home/daytona/app/results.json

## Related Pages

- [Claude Code MCP leaderboard](/leaderboard/claudecode/mcp)
- [Compare Claude Code MCP companies](/leaderboard/claudecode/mcp/compare)
- [Agent Landscape](/leaderboard/discoverability)

Canonical URL: https://devtoolarena.com/claudecode/mcp/cloudflare