# Cursor MCP connection failed

This page connects **BugTape's hosted MCP** at `https://app.bugtape.ai/mcp`. It is not a directory of other MCP servers. For Cursor's own client behaviour, use [Cursor's MCP docs](https://cursor.com/docs/mcp) and stop there.

## Check these first

| What you see | What it usually means |
|---|---|
| **Needs login** stays on screen | OAuth did not finish. Open the browser step, pick the workspace, click **Allow**. |
| Invalid JSON | `.cursor/mcp.json` or `~/.cursor/mcp.json` does not parse. The shapes are below. |
| stdio `ENOENT`, or `npx` cannot start | A local command server needs Node on that machine. BugTape's door is a URL, so you can skip the local spawn. |
| 401 | The `Authorization` header is missing or expired. The token must be `bt_pat_…`. |
| You pasted `bt_live_` or `bt_test_` | Rejected by design. Those keys only send reports. Make an agent token. |
| Bare `GET /mcp` returns 405 `SUBSCRIBE_STREAM_REQUIRES_RESOURCE` | Expected. A stream needs `listen`, or `GET /mcp?resource=…`. The error is in [MCP tools](/docs/mcp-tools/). |
| `listen` is refused on Free | Live wait needs Pro or prepaid credits. Call `list_recommended_critical` instead. |

## Connect BugTape

Fastest reset:

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

Or OAuth, with no token in the file:

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

Or a bearer token you created on the Team page. Never commit it. Prefer `~/.cursor/mcp.json` over the project file when the token is present.

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

Project config is `.cursor/mcp.json`. User config is `~/.cursor/mcp.json`. The URL has to be exactly `https://app.bugtape.ai/mcp`.

[Start free](/console/register?utm_source=bugtape_seo&utm_campaign=cursor-mcp-connection-failed) if you do not have a workspace yet. No card.

## Why a remote URL skips the local spawn

BugTape MCP is HTTP. Cursor opens the URL. You do not need a local `npx` process, a path to `node`, or a working stdio spawn for this server. That is the whole reason to use the URL above. Other vendors' servers are out of scope for this page.

## Confirm it worked

The Team page lists the agent. Then paste:

> Call `subscribe_feed` with `urgent_critical`, then `list_recommended_critical`, then `get_repro_context` for the top issue. Do not start with `list_bugs`.

## 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/).

## Still stuck

Follow [MCP install](/docs/mcp-install/) from the top. Write to hi@bugtape.ai from the address on your workspace. This page does not promise a response time. What we do publish about support is on [Trust](/trust/).

Next, once the socket is up: [Connect Cursor](/connect/cursor/) · [Cursor bug reports](/cursor/bug-reports/) · [MCP tools](/docs/mcp-tools/).

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