# Cloudflare Logpush MCP server
> Check the health of Cloudflare Logpush jobs and find failing or erroring jobs across your accounts.
- Listing: https://mcp.tc/i/cloudflare-logpush
- Connect: use the server's own URL `https://logs.mcp.cloudflare.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: Cloudflare
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage:
- Repository:
## About
Connects to the Cloudflare Logpush API so an assistant can fetch Logpush jobs for a specific account or for all accounts a user can access. It helps you see which jobs are enabled, which have failed recently and which report errors.
Runs as a hosted remote endpoint at https://logs.mcp.cloudflare.com/mcp using streamable HTTP. Sign in with your Cloudflare account through the OAuth flow in your browser. No local install or API key is needed. The server is described as a work in progress, with more tools planned.
## What it can do
- List Logpush jobs for one account or all accounts you can access
- Find Logpush jobs that failed recently
- Spot jobs with errors in your account
- Review which jobs are enabled and their failures
## Example prompts
- "Which Logpush jobs failed recently?"
- "Do any of my Logpush jobs in my account have errors?"
- "Can you list all the enabled job failures from today?"
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http cloudflare-logpush https://logs.mcp.cloudflare.com/mcp
```
2. Start Claude Code, type `/mcp`, pick **cloudflare-logpush** and choose **Authenticate**. A browser window opens for the Cloudflare sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Settings → Connectors** and click **Add custom connector**.
2. Name it **Cloudflare Logpush** and paste this URL:
```url
https://logs.mcp.cloudflare.com/mcp
```
3. Click **Add**, then **Connect**, and sign in when Cloudflare asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://logs.mcp.cloudflare.com/mcp` and click **Add**.
3. Click **Connect** and sign in when Cloudflare asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.
2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.
3. Paste `https://logs.mcp.cloudflare.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Cloudflare to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"cloudflare-logpush": {
"url": "https://logs.mcp.cloudflare.com/mcp"
}
}
}
```
Cursor shows **Needs login** next to the server. Click it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"cloudflare-logpush","type":"http","url":"https://logs.mcp.cloudflare.com/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"cloudflare-logpush": {
"type": "http",
"url": "https://logs.mcp.cloudflare.com/mcp"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"cloudflare-logpush": {
"serverUrl": "https://logs.mcp.cloudflare.com/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add cloudflare-logpush --url https://logs.mcp.cloudflare.com/mcp
codex mcp login cloudflare-logpush
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.cloudflare-logpush]
url = "https://logs.mcp.cloudflare.com/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http cloudflare-logpush https://logs.mcp.cloudflare.com/mcp
```
Then, inside Gemini CLI, run `/mcp auth cloudflare-logpush` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"cloudflare-logpush": {
"type": "http",
"url": "https://logs.mcp.cloudflare.com/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://logs.mcp.cloudflare.com/mcp`.
## Details
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03
---
Source: https://mcp.tc/i/cloudflare-logpush (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report