zeekay
f9fdfcd098
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.
Cloudflare Logpush 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 the Cloudflare Logpush API to provide insights into Logpush jobs.
🔨 Available Tools
Currently available tools:
| Category | Tool | Description |
|---|---|---|
| Logpush Jobs By Account | logpush_jobs_by_account_id |
Fetches Logpush jobs by specific account or all accounts under the user |
This MCP server is still a work in progress, and we plan to add more tools in the future.
Prompt Examples
Which Logpush jobs failed recently?Do any of my Logpush jobs in my <insert name> account have errors?Can you list all the enabled job failures from today?
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://logs.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://logs.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.