# Connect BugTape MCP to Cursor

After Cursor can see BugTape, the agent reads a ranked inbox, pulls the evidence for one issue, and can open a pull request. A human reviews that pull request. BugTape then checks the fix in the release you ship.

The door is the hosted MCP server at `https://app.bugtape.ai/mcp`. It is a remote HTTP server. You do not spawn a local stdio process for BugTape.

## One command

```bash
npx -y bugtape connect cursor
```

The CLI prints a link and a code. Open the link, check the code, and click **Allow**. The agent shows up on the Team page, where you can remove it. `--global` writes the user-level Cursor config. The command is the one in [MCP install](/docs/mcp-install/) and the [CLI docs](/docs/cli/). The tarball name is `bugtape-0.1.1.tgz` until those docs change.

## OAuth in mcp.json

Project file: `.cursor/mcp.json`. User file: `~/.cursor/mcp.json`. Prefer the user file when the token would otherwise be committed.

```json
{
  "mcpServers": {
    "bugtape": {
      "url": "https://app.bugtape.ai/mcp"
    }
  }
}
```

Cursor shows **Needs login**. Finish **Allow** in the browser and pick the workspace.

## With an agent token

Create the token on Team → Add an agent, or with `npx -y bugtape login`. The header value is `Bearer bt_pat_…`. A capture key will be rejected.

```json
{
  "mcpServers": {
    "bugtape": {
      "url": "https://app.bugtape.ai/mcp",
      "headers": {
        "Authorization": "Bearer bt_pat_YOUR_TOKEN"
      }
    }
  }
}
```

**Pick up and fix** includes `get_repro_context` and `suggest_fix`. **Follow and read** drops `suggest_fix`. Sign-in can add `create_bug` and, if you tick it, `setup_capture`. Those are permissions, not a `subscribe` tool. [MCP tools](/docs/mcp-tools/).

## Plans and credits

MCP works on every plan, including Free. On Free and Prepaid credits, each agent read of a bug's captured events costs 2 credits. Free includes 150 credits a month. On Pro ($29 USD a month) those reads are free. A prepaid pack costs $10 USD for 2,000 credits. Detail is on [Pricing](/pricing/).

`listen` (the live wait for the next bug) needs Pro, or prepaid credits on the workspace. On Free without those credits, start with `list_recommended_critical`. Do not start with `list_bugs`.

Capture keys (`bt_live_` / `bt_test_`) are rejected for MCP. They only send reports. The agent uses OAuth or a `bt_pat_` token. [MCP install](/docs/mcp-install/) · [MCP tools](/docs/mcp-tools/).

## First prompt

Paste this after the connection is up:

> Call `subscribe_feed` with `deliveryFeed: "urgent_critical"` and `notify: true`. Then call `list_recommended_critical`, take the top issue, and call `get_repro_context` for it. Report the evidence and any gaps. If this workspace can use `listen`, call it on `bugtape://projects/{projectId}/inbox`. Do not start with `list_bugs`.

Also paste the [AGENTS.md snippet](/docs/examples/AGENTS.md) into the repo.

## When the connection fails

Use the [Cursor MCP connection checklist](/guides/cursor-mcp-connection-failed/). It ends at this same hosted URL. What the agent should do with a real bug is [Cursor bug reports](/cursor/bug-reports/). If you already run Sentry, read [BugTape vs Sentry](/vs/sentry/) before you remove anything. You can keep both.

Codex and Grok can use the same hosted door (`connect codex`, `connect grok`). Grok's web connectors are reported not to finish OAuth; use the CLI or a token, as the install doc says.

[Start free](/console/register?utm_source=bugtape_seo&utm_campaign=connect-cursor) — no card. Narrative install post: [Install BugTape MCP](/blog/install-bugtape-mcp-claude-cursor-codex/).

Your team reviews the PR. Agents do not silent-ship.