# BugHerd MCP server

> Triage and resolve BugHerd website feedback tasks from your AI coding agent, then post updates to task threads.

- Listing: https://mcp.tc/i/bugherd
- Connect: use the server's own URL `https://mcp.bugherd.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: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: BugHerd
- Homepage: <https://bugherd.com/feature/mcp>

## About

Connects an AI assistant to BugHerd, the website feedback and bug tracking tool. The assistant can list open tasks on a project, read each task with its screenshot, URL, CSS selector and client comments, act on it, mark it done and post a summary to the task thread.

It runs as a hosted streamable HTTP endpoint at mcp.bugherd.com. Users sign in with OAuth, and no API key is needed. The BugHerd MCP feature is in beta and works with clients such as Claude Code, Cursor, ChatGPT and VS Code.

## What it can do

- List open tasks on a BugHerd project
- Read task details including screenshots, URL and CSS selector
- Read client comments and attachments
- Mark tasks as done
- Post summary comments to task threads

## Example prompts

- "Work through the open tasks on the Henderson project."
- "List all open BugHerd tasks for my latest project."
- "Read the client comment on this task and fix the CSS issue."
- "Mark task 42 done and post a summary to its thread."

## Install

### Claude Code

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

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

2. Start Claude Code, type `/mcp`, pick **bugherd** and choose **Authenticate**. A browser window opens for the BugHerd sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **BugHerd** and paste this URL:

```url
https://mcp.bugherd.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when BugHerd 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=BugHerd&connectorUrl=https%3A%2F%2Fmcp.bugherd.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.bugherd.com/mcp` and click **Add**.

3. Click **Connect** and sign in when BugHerd 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, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.bugherd.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to BugHerd to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=bugherd&config=eyJ1cmwiOiJodHRwczovL21jcC5idWdoZXJkLmNvbS9tY3AifQ%3D%3D>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "bugherd": {
      "url": "https://mcp.bugherd.com/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

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

Or from a terminal:

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

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

`.vscode/mcp.json`:

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

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

`config.toml`:

```toml
[mcp_servers.bugherd]
url = "https://mcp.bugherd.com/mcp"
```

### Gemini CLI

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

Then, inside Gemini CLI, run `/mcp auth bugherd` 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": {
    "bugherd": {
      "type": "http",
      "url": "https://mcp.bugherd.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://mcp.bugherd.com/mcp`.

## Details

- Server version: 1.1.0
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/bugherd (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
