A version written into a manifest is written into every manifest that wants it, which is how eslint came to exist in a hundred and four forms across this estate and how a package came to resolve twice at run time. The catalog moves the number out of the manifest: a manifest names the package, the workspace names the version. Four are held below their latest because the newer release cannot be used, and the reason is recorded rather than the version alone: @noble/hashes 2 renamed every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels 3 points its types condition at the bundle.
Workers Observability MCP Server ðŸ”
This is a Model Context Protocol (MCP) server that supports remote MCP connections, with Cloudflare OAuth built-in.
It integrates tools powered by Workers Observability to provide global Internet traffic insights, trends and other utilities.
🔨 Available Tools
Currently available tools:
| Category | Tool | Description |
|---|---|---|
| Workers Analytics | query_worker_observability |
Queries Workers Observability API to analyze logs and metrics from your Cloudflare Workers. Supports listing events, calculating metrics, and finding specific invocations |
| Schema Discovery | observability_keys |
Discovers available data fields in your Workers logs including metadata fields, worker-specific fields, and custom logged fields |
| Value Exploration | observability_values |
Finds available values for specific fields in Workers logs to help build precise filters for analytics queries |
This MCP server is still a work in progress, and we plan to add more tools in the future.
Prompt Examples
Can you tell me about any potential issues on this particular worker 'my-worker-name'?Show me the CPU time usage for my worker 'api-gateway' over the last 24 hoursWhat were the top 5 countries by request count for my worker yesterday?How many requests were made to my worker 'my-app' broken down by HTTP status code?Compare the error rates between my production and staging workers
Access the remote MCP server from any MCP Client
If your MCP client has first class support for remote MCP servers, the client will provide a way to accept the server URL (https://observability.mcp.cloudflare.com) directly within its interface (for example in Cloudflare AI Playground).
If your client does not yet support remote MCP servers, you will need to set up its resepective configuration file using mcp-remote to specify which servers your client can access.
Replace the content with the following configuration:
{
"mcpServers": {
"cloudflare": {
"command": "npx",
"args": ["mcp-remote", "https://observability.mcp.cloudflare.com/sse"]
}
}
}
Once you've set up your configuration file, restart MCP client and a browser window will open showing your OAuth login page. Proceed through the authentication flow to grant the client access to your MCP server. After you grant access, the tools will become available for you to use.
Interested in contributing, and running this server locally? See CONTRIBUTING.md to get started.