Cloudflare Observability MCP Server

🛡️ Official✓ VerifiedHTTP + SSEOAuth 2.13 tools·Online11ms·30d uptime: 100%·Last checked 18m ago

The Observability MCP exposes Workers logs, traces and error analytics to agents — ask why a Worker is failing and get data back, after OAuth authorization.

https://observability.mcp.cloudflare.com/mcp

SSEhttps://observability.mcp.cloudflare.com/sse

Provider: Cloudflare ↗
Source: https://github.com/cloudflare/mcp-server-cloudflare ↗
Categories: ☁️ Cloud, Infrastructure & DevOps

中文简介

Cloudflare 认证版可观测性 MCP 服务器。可从任意 MCP 客户端查询 Worker 日志、链路事件与错误分析。

HTTP + SSEhttps://observability.mcp.cloudflare.com/mcp

Legacy SSE endpoint

SSEhttps://observability.mcp.cloudflare.com/sse

Install in Cursor →

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "cloudflare-observability": {
      "url": "https://observability.mcp.cloudflare.com/mcp"
    }
  }
}

🔬 Test Live in Online Inspector 🔐 Audit OAuth 2.1 Config

🧰 Tools exposed by Cloudflare Observability MCP (3)

Tool	Safety	Description	Parameters
query_worker_logs	🟢 Read	Query recent logs (invocations, exceptions, console output) for a Worker.	scriptName*: stringfilter: stringminutes: number
list_Trace_events	🟢 Read	List trace events captured by Workers observability.	scriptName: stringlimit: number
get_error_analytics	🟢 Read	Get error-rate analytics for Workers in the account.	scriptName: stringdays: number

🔐 OAuth 2.1 & Security

Auth type: OAuth 2.1
Dynamic Client Registration: ✅ Supported
PKCE S256: ✅ Supported
Protected resource metadata: https://observability.mcp.cloudflare.com/.well-known/oauth-protected-resource (expected location)

🔐 Audit OAuth 2.1 Config →

🧩 Recommended Agent Skills

Observability skills ↗

📖 Guide

Cloudflare Observability MCP — Remote MCP Server

Cloudflare's Observability MCP turns your Workers telemetry into agent tools: query recent Worker logs, list trace events and pull error analytics. Combined with an agent's code context it makes 'why is my Worker 500ing' a one-prompt investigation.

Endpoint & Transport

Endpoint URL: https://observability.mcp.cloudflare.com/mcp
Legacy SSE endpoint: https://observability.mcp.cloudflare.com/sse
Transport: Streamable HTTP + legacy SSE

Authentication

Cloudflare Observability MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.

Available Tools (3)

Tool	Safety	Description
`query_worker_logs`	read	Query recent logs (invocations, exceptions, console output) for a Worker.
`list_Trace_events`	read	List trace events captured by Workers observability.
`get_error_analytics`	read	Get error-rate analytics for Workers in the account.

Connect in 30 Seconds

Claude Code — one command:

claude mcp add --transport http cloudflare-observability https://observability.mcp.cloudflare.com/mcp

Cursor — add to ~/.cursor/mcp.json:

{ "mcpServers": { "cloudflare-observability": { "url": "https://observability.mcp.cloudflare.com/mcp" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "cloudflare-observability": { "type": "http", "url": "https://observability.mcp.cloudflare.com/mcp" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

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

On first connect your client opens a browser OAuth consent screen — approve it and tools become available immediately.

Troubleshooting

401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
Which URL should I use? Prefer https://observability.mcp.cloudflare.com/mcp (Streamable HTTP). The SSE URL is only for older clients pinned to the pre-2025-03-26 spec.
"Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
Requires OAuth — telemetry is scoped to the authorizing account's data.
Log retention follows your Cloudflare plan's observability limits.

🚀 How to Connect

Copy the Cloudflare Observability MCP endpoint URL
The remote endpoint is https://observability.mcp.cloudflare.com/mcp. A legacy SSE endpoint is also available at https://observability.mcp.cloudflare.com/sse.
Add it to your MCP client
Claude Code: claude mcp add --transport http cloudflare-observability https://observability.mcp.cloudflare.com/mcp. Cursor: add "cloudflare-observability": { "url": "https://observability.mcp.cloudflare.com/mcp" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
Complete the OAuth consent
On first connection your client opens a Cloudflare consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
Verify with the online inspector
Paste https://observability.mcp.cloudflare.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Cloudflare Observability MCP's 3 tools respond.

❓ FAQ

What is the Cloudflare Observability MCP remote MCP endpoint?

The primary endpoint is https://observability.mcp.cloudflare.com/mcp, with a legacy SSE endpoint at https://observability.mcp.cloudflare.com/sse. It is an official first-party server operated by Cloudflare, speaking the Streamable HTTP + legacy SSE transport.

Should I use Cloudflare Observability MCP's /mcp or /sse endpoint?

Use https://observability.mcp.cloudflare.com/mcp — Streamable HTTP is the current MCP transport and what every modern client defaults to. https://observability.mcp.cloudflare.com/sse exists only for clients still on the legacy HTTP+SSE transport from the 2024 spec.

How do I authenticate with Cloudflare Observability MCP?

Cloudflare Observability MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.

I'm getting a 401 Unauthorized from Cloudflare Observability MCP — what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with Cloudflare Observability MCP?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http cloudflare-observability https://observability.mcp.cloudflare.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.

What tools does Cloudflare Observability MCP expose?

3 tools are cataloged in this directory — including `query_worker_logs`, `list_Trace_events`, `get_error_analytics`. Use our online inspector to fetch the live tool list straight from the endpoint.

🔗 Connect Guides

Cursor

Connect Cloudflare Observability MCP →

Claude

Connect Cloudflare Observability MCP →

Claude Code

Connect Cloudflare Observability MCP →

VS Code

Connect Cloudflare Observability MCP →

ChatGPT

Connect Cloudflare Observability MCP →

Windsurf

Connect Cloudflare Observability MCP →

📛 Embed Status Badge in README

[![Remote MCP Status](https://remotemcp.net/api/badge/status/cloudflare-observability.svg)](https://remotemcp.net/servers/cloudflare-observability)

[![Test in Inspector](https://remotemcp.net/api/badge/inspect/cloudflare-observability.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fobservability.mcp.cloudflare.com%2Fmcp)