How is this different from connecting Cloudflare Observability MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Cloudflare Observability MCP API changes?

We track the Cloudflare Observability MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Cloudflare Observability tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Cloudflare Observability?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Cloudflare Observability MCP server myself?

No. TrustGate connects to the Cloudflare Observability MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Cloudflare Observability directly.

Connect Cloudflare Observability MCP to your AI agents, securely.

Q: Is Cloudflare Observability MCP secure?

The server itself exposes 8 tools, and some of them can write to your Cloudflare Observability account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Cloudflare Observability.

One secured endpoint for every Cloudflare Observability call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Cloudflare Observability MCP now

What your agents can ask once Cloudflare Observability MCP is connected.

“Tell me about any potential issues on this worker”
“Compare error rates between my production and staging workers”
“Which fields are available in my Workers logs?”

“List the Workers in my account”
“Show the invocations that failed in the last hour”
“Get the source code of this Worker”

Select the tools your AI agents can call

8 tools from the Cloudflare Observability MCP schema.

Showing 8 tools

query_worker_observabilityreadQuery the Workers Observability API to analyze logs and metrics from your Cloudflare Workers. Supports listing events, calculating metrics, and finding specific invocations.
observability_keysreadDiscovers available data fields in your Workers logs, including metadata fields, worker-specific fields, and custom logged fields.
observability_valuesreadFinds available values for specific fields in Workers logs to help build precise filters for analytics queries.
workers_listreadList all Workers in your Cloudflare account.
workers_get_workerreadGet the details of a Cloudflare Worker.
workers_get_worker_codereadGet the source code of a Cloudflare Worker.
search_cloudflare_documentationreadSearch the Cloudflare documentation.
migrate_pages_to_workers_guidereadRead the guide before migrating Pages projects to Workers.

What Cloudflare Observability MCP exposes

Cloudflare Observability MCP groups its 8 tools into 3 categories, each with a suggested starting policy.

Category	Covers	Access	Suggested policy
Observability	Log and metric queries, field key discovery and value exploration	Read	Limit access to intended accounts
Workers	Worker listing, details and source code	Read	Restrict access to source code
Account & Docs	Account listing, documentation search and migration guides	Read	Allow documentation searches