BugTape docs

Install BugTape MCP

Connect Claude Code, Cursor, Codex or any HTTP MCP client on Pro.

BugTape MCP is a remote HTTP server. Pro plan required, or Pay as you go with prepaid credits (each agent read of a bug's captured events costs 2 credits; other reads are free). Use an agent PAT (bt_pat_…) minted in Settings → Agents. Capture keys (bt_live_ / bt_test_) are rejected.

Endpoint: https://app.bugtape.ai/mcp

Default tools for a new token: subscribe + get_repro_context. Start with list_recommended_critical, then get_repro_context. Do not dump list_bugs.

Updated: 2026-09-20.

Claude Code

claude mcp add --transport http bugtape https://app.bugtape.ai/mcp \
  --header "Authorization: Bearer bt_pat_YOUR_TOKEN"

Cursor

Save in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user):

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

Codex

Set BUGTAPE_MCP_TOKEN in the environment that launches Codex. Load it from your password manager or OS keychain. Do not put the PAT in shell history, config.toml, source files, or the repository.

codex mcp add bugtape \
  --url https://app.bugtape.ai/mcp \
  --bearer-token-env-var BUGTAPE_MCP_TOKEN

Codex stores the URL and environment variable name in its TOML configuration, then reads the token from BUGTAPE_MCP_TOKEN when it connects. Cursor uses the mcpServers JSON above; do not use that JSON for Codex.

Grok / HTTP MCP

Point the client at https://app.bugtape.ai/mcp with header Authorization: Bearer bt_pat_YOUR_TOKEN. Same JSON shape as Cursor.

After connect

First useful request: “Call list_recommended_critical, select the highest-ranked issue, then call get_repro_context for that issue. Report the captured evidence and any gaps.” Do not start with a dump of list_bugs.

Paste the AGENTS.md snippet into the repo so the agent uses the ranked inbox. Full contract: Agent setup. Tool list: MCP tools.

Directory listings

Machine files for MCP directories: mcp.json and smithery.yaml. Submitting them to Smithery, PulseMCP, mcp.so, Cursor directory, Claude connectors, and Glama is a manual step. The public URL and auth header above are the source of truth.