# Cloudflare Workers Builds MCP server

> Inspect Cloudflare Workers builds, view build details and read build logs from your assistant.

- Listing: https://mcp.tc/i/cloudflare-builds
- Connect: use the server's own URL `https://builds.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: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- 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: <https://developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/>
- Repository: <https://github.com/cloudflare/mcp-server-cloudflare/tree/main/apps/workers-builds>

## About

Connects to Cloudflare Workers Builds so an assistant can list builds for a Worker, look up a specific build by UUID including its build and deploy commands, and fetch build logs. It helps check whether the latest build of a Worker succeeded and why a build failed.

It runs as a hosted remote server at https://builds.mcp.cloudflare.com/mcp using streamable HTTP. Sign in with your Cloudflare account through the OAuth flow in your browser when your client prompts. Every tool call names its Worker or build explicitly. The server is described as a work in progress, with more tools planned.

## What it can do

- List builds for a Cloudflare Worker
- Get details of a build by UUID, including build and deploy commands
- Fetch logs for a Workers build
- Check whether the latest build of a Worker succeeded

## Example prompts

- "List the last 5 builds for my worker 'my-ci-worker'."
- "What were the details for build 'xxxx-xxxx-xxxx-xxxx'?"
- "Show me the logs for build 'xxxx-xxxx-xxxx-xxxx'."
- "Did the latest build for worker frontend-app succeed?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http cloudflare-builds https://builds.mcp.cloudflare.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **cloudflare-builds** 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 Workers Builds** and paste this URL:

```url
https://builds.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](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Cloudflare%20Workers%20Builds&connectorUrl=https%3A%2F%2Fbuilds.mcp.cloudflare.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://builds.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://builds.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](<https://cursor.com/install-mcp?name=cloudflare-builds&config=eyJ1cmwiOiJodHRwczovL2J1aWxkcy5tY3AuY2xvdWRmbGFyZS5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "cloudflare-builds": {
      "url": "https://builds.mcp.cloudflare.com/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=cloudflare-builds&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fbuilds.mcp.cloudflare.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"cloudflare-builds","type":"http","url":"https://builds.mcp.cloudflare.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "cloudflare-builds": {
      "type": "http",
      "url": "https://builds.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-builds": {
      "serverUrl": "https://builds.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-builds --url https://builds.mcp.cloudflare.com/mcp
codex mcp login cloudflare-builds
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.cloudflare-builds]
url = "https://builds.mcp.cloudflare.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http cloudflare-builds https://builds.mcp.cloudflare.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth cloudflare-builds` 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-builds": {
      "type": "http",
      "url": "https://builds.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://builds.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-builds (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report