Cloudflare Observability
Query Cloudflare Workers logs, analytics, and errors to debug your applications. Sign in with Cloudflare to connect.
What Cloudflare Observability exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the cloudflare-observability__ namespace. Your agent never loads them all — it searches, and gets the few that match.
cloudflare-observability__migrate_pages_to_workers_guideno arguments
ALWAYS read this guide before migrating Pages projects to Workers.
cloudflare-observability__observability_keys1 argument · 1 required
Find keys in the Workers Observability Data ## Best Practices - Set a high limit (1000+) to ensure you see all available keys - Add the $metadata.service filter to narrow results to a specific Worker ## Troubleshooting - If expected fields are missing, verify the Worker is actively logging - For empty results, try broadening your time range
Required
keysQuerycloudflare-observability__observability_values1 argument · 1 required
Find values in the Workers Observability Data. ## Troubleshooting - For no results, verify the field exists using observability_keys first - If expected values are missing, try broadening your time range
Required
valuesQuerycloudflare-observability__query_worker_observability1 argument · 1 required
Query the Workers Observability API to analyze logs and metrics from your Cloudflare Workers. * A query typical query looks like this: {"view":"events","queryId":"workers-logs-events","limit":5,"dry":true,"parameters":{"datasets":["cloudflare-workers"],"filters":[{"id":"520","key":"message","operation":"eq","type":"string","value":"Clickhouse Statistics"},{"id":"2088","key":"statistics.elapsed","operation":"gt","type":"number","value":"0.269481519"}],"calculations":[],"groupBys":[],"havings":[]},"timeframe":{"to":"2025-04-30T20:53:15Z","from":" ""2025-04-30T19:53:15Z"}} ## Core Capabilities This tool provides three primary views of your Worker data: 1. **List Events** - Browse individual request logs and errors 2. **Calculate Metrics** - Compute statistics across requests (avg, p99, etc.) 3. **Find Specific Invocations** - Locate individual requests matching criteria ## Filtering Best Practices - Before applying filters, use the observability_keys and observability_values tools to confirm available filter fields and the correct filter value to add unless you have the data in a response from a previous query. - Common filter fields: $metadata.service, $metadata.trigger, $metadata.message, $metadata.level, $metadata.requestId, ## Calculation Best Practices - Before applying calculations, use the observability_keys tools to confirm key that should be used for the calculation ## Troubleshooting - If no results are returned, suggest broadening the time range or relaxing filters - For errors about invalid fields, recommend using observability_keys to see available options
Required
querycloudflare-observability__search_cloudflare_documentation1 argument · 1 required
Search the Cloudflare documentation. This tool should be used to answer any question about Cloudflare products or features, including: - Workers, Pages, R2, Images, Stream, D1, Durable Objects, KV, Workflows, Hyperdrive, Queues - AI Search, Workers AI, Vectorize, AI Gateway, Browser Run - Zero Trust, Access, Tunnel, Gateway, Browser Isolation, WARP, DDOS, Magic Transit, Magic WAN - CDN, Cache, DNS, Zaraz, Argo, Rulesets, Terraform, Account and Billing Results are returned as semantically similar chunks to the query.
Required
querycloudflare-observability__workers_get_worker1 argument · 1 required
Get the details of the Cloudflare Worker.
Required
scriptNamecloudflare-observability__workers_get_worker_code1 argument · 1 required
Get the source code of a Cloudflare Worker. Note: This may be a bundled version of the worker.
Required
scriptNamecloudflare-observability__workers_listno arguments
List all Workers in your Cloudflare account. If you only need details of a single Worker, use workers_get_worker.
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Switch Cloudflare Observability on
Authorize it from your library; the grant is yours and stays yours.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.
