Clarify that observability/sse endpoint only supports observability — not full API access

[Zilong-L]

Hi team,

I wanted to flag a potential point of confusion in the README.

Right after listing powerful example use cases like:

Please deploy me a new Worker with an example durable object.
Can you tell me about the data in my D1 database named '...'?
Can you copy all the entries from my KV namespace '...' into my R2 bucket '...'?

…the instructions recommend configuring Claude Desktop to use:

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.cloudflare.com/workers/observability/sse"
      ]
    }
  }
}

However, this endpoint (observability/sse) only supports observability-related commands (like logs and telemetry), not the broader Cloudflare API access mentioned above (like D1, KV, R2, or deploying Workers).

For users looking for full MCP integration with Cloudflare's API, the correct setup is to use the local package:

@cloudflare/mcp-server-cloudflare

This local server allows us to authenticate with OAuth client and access the full range of Cloudflare features via MCP.

Would be great to clarify this in the README to help guide users to the right path based on their needs.

Also I have a question that why is it called the "deprecated local only cloudflare-mcp-server"?

Thanks again for all the work on this!

[Maximo-Guk]

Hey @Zilong-L 👋, I've updated the README.md to clarify that we're working on gradually moving over tools to this remote MCP server repo. In the meantime if you need more tools, feel free to use the local only mcp-server-cloudflare package which currently has more tools available.

[Maximo-Guk]

Hi @Zilong-L , I would check out our bindings server which now contains most of this functionality!