Install

Install BugTape MCP in Claude Code

One command connects Claude Code to BugTape hosted MCP. Ranked inbox, evidence, ack with a PR URL, and a human reviews the pull request.

One command connects Claude Code to BugTape's hosted MCP. The agent can then read a ranked inbox, pull evidence, and open a pull request. A human reviews it. The server is https://app.bugtape.ai/mcp, not a local stdio program.

One command

npx -y bugtape connect claude

You get a link and a code. Open the link on any machine, check the code, click Allow. This works when the agent machine has no browser. The same CLI with init can add capture to the repo. CLI · MCP install. The tarball in this command is bugtape-0.1.1.tgz, matching those docs.

OAuth with the Claude Code CLI

claude mcp add --transport http bugtape https://app.bugtape.ai/mcp

Then run /mcp in Claude Code and choose BugTape.

With an agent token

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

Use a bt_pat_ token from Team → Add an agent. bt_live_ and bt_test_ keys are for ingest. MCP rejects them.

Headless and cloud agents can use the link-and-code flow above, so the token need not sit in the agent environment. If you do pass a header, keep the token out of the repo.

What the agent may do

Agent tokens can read evidence and acknowledge work (ack_bug, including prUrl). They cannot call update_bug, merge_bugs, delete_bug or add_comment. Those stay on a human session. 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.

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 · MCP tools.

First prompt

Call subscribe_feed with urgent_critical, then list_recommended_critical. For the top issue, call get_repro_context. Summarise the evidence. Use listen on the project inbox only when this plan allows it. Do not dump list_bugs.

Paste the AGENTS.md snippet so the next session starts at the ranked inbox.

Cursor has its own page: Connect Cursor. A failed Cursor socket is connection failed. Codex uses connect codex with BUGTAPE_MCP_TOKEN in the environment, documented in MCP install. Grok's web app may not finish OAuth; the install doc says to use connect grok or a token.

If Sentry MCP is already connected, you can leave it. BugTape vs Sentry.

Start free — no card. The same steps in a post: Install BugTape MCP.

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