Which AI clients can use the Cloudflare Observability MCP server?

27 AI clients, including Cursor, VS Code, and Claude. Each connects to Cloudflare Observability as a remote MCP server through Runlayer, which adds identity, policy, scanning, and audit to every call.

Which Cloudflare Observability tools are available?

Cloudflare Observability reports its tools when your organization connects it. Admins then choose which ones each group can call.

How does Cloudflare Observability authenticate?

Sign in the way Cloudflare Observability requires. Runlayer holds the credentials so they stay out of the client’s configuration.

Integrations / MCP servers

Cloudflare Observability

Debug and get insight into your application's logs and analytics

Book a demo View documentation

Tools

Tools discovered when you connect

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

Tools load when your organization connects this server

Cloudflare Observability can expose tools based on its deployed version and credentials. Runlayer discovers the available list when your organization connects the server.

Compatibility

Connect Cloudflare Observability to the clients your teams already use

27 AI clients can connect to Cloudflare Observability through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Cloudflare Observability through Runlayer?

One approved path

Approve Cloudflare Observability once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.