BugTape docs

BugTape MCP tools

Every tool, its inputs and scopes.

Public tool list for agents connecting over the hosted MCP door. Delivery paths (listen vs webhook vs poll) live in agents.md.

Remote door

• URL: https://app.bugtape.ai/mcp
• RPC: POST for initialize / tools / resources (JSON-RPC, stateless)
• Listen: GET may open an SSE stream with keep-alive (not a second RPC door)

Authorization: Bearer bt_pat_…

Ingest keys (bt_live_… / bt_test_…) are rejected — they are for SDK ingest only. MCP requires a Pro+ org (features.mcp).

Example client shape (field names vary by host):

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

Org-scoped agent PATs inherit organization on the API — BUGTAPE_ORG_ID / X-BugTape-Org are optional when the PAT is set.

Authentication (do not invent a seventh model)

There is no PAT→JWT mint. Request Bearer PATs are request-scoped.

Agent PATs may call the agent verbs (create_bug, ack_bug, listen / resources/subscribe), the evidence tools (get_repro_context, suggest_fix, get_bug, get_bug_events, get_occurrence_files, get_screenshot, get_bug_occurrences, get_bug_history, get_similar_bugs) and the read-only routing tools (list_recommended_critical, list_bugs, list_bug_groups, search_bugs, get_live_occurrences, get_bug_users, get_user_timeline, list_projects, get_project_stats, get_current_org, get_credit_usage). Ordinary issue mutations — update_bug, bulk_update_bugs, delete_bug, merge_bugs, add_comment, watch_bug / unwatch_bug — stay human-only. Separately, PATs with the named work actions and a current project grant can claim work and submit/promote verification through the tools below. There is no agent_resolved tool.

Tools

Bug management

Claims and trusted verification

Verified Close: a fixer PAT records a proposal, then a different verifier PAT records an explicit replay_assert observation against the same evidence_hash. This credential separation prevents one PAT from self-verifying. It does not establish separate agent identity, require measured artifacts, or set verified_fixed.

Flow: fixer PAT claim_issue → bind pack/contract (evidence_hash) → propose_fix (never closes, never sets verified_fixed) → different PAT verify_fix with explicit observation.reproduced. Same fixer token on verify → E_SELF_VERIFY. Use prepare_verification / submit_verification / promote_verification for enrolled, signed, scope-wide measured proof. On MCP-related failure packs, census_stamp is a first-class optional field — record it when present. watch_bug stays human. Narrative: agents.md — Verified Close.

These tools require a current PAT and explicit project work grant. Actions and grants are rechecked on each call. Keep claim generation and fencingToken as strings. A capture key cannot call them. See the public runner contract and offline signer for exact signing bytes, evidence upload, enrollment, and retries.

register_verification_runner, register_verification_device, list_verification_enrollment, revoke_verification_runner, and revoke_verification_device require a human organization admin session. They do not let an agent create its own trust. Send only public runner keys. Device/runtime enrollment is explicit; simulator results cannot prove physical-device behavior.

Artifact reservation/upload is a separate HTTP capability. A PAT needs create_bug and a current project grant to write its CI log; submit_verification alone is insufficient. Check storage capabilities and ready/hash state. Application/build/installation registry management remains human manager/admin only.

Events & analysis

Users & live feed

Projects & org

Comments & watchers

MCP subscriptions (agent listen)

1. resources/subscribe on bugtape://bugs/{bugId}/status, bare bugtape://bugs/{bugId}, or bugtape://projects/{projectId}/inbox
2. Receive _meta["io.modelcontextprotocol/subscriptionId"] and notifications/subscriptions/acknowledged
3. Handle notifications/resources/updated, then resources/read — inbox pings are bug-level (new fingerprint), not occurrence-level
4. Or call listen (optional afterCursor for durable Tuesday-queue catch-up; pass an inbox resourceUri to wait/replay new-bug and agent_notify events)
5. agent_notify means a human or the project's auto-notify handed you this bug. Read get_repro_context, ack_bug working, and ack_bug working with prUrl once you open the PR. The MCP server reads handoffs from GET /v1/projects/{projectId}/agent-notifications (subscribe scope); collecting one marks it delivered on the issue page.

GET /mcp for SSE requires Accept: text/event-stream, an explicit subscribe-scoped Bearer PAT, and 1–32 resource query values from the same workspace. No resource filter returns 405 so standard MCP clients can continue with POST tools.

See agents.md for the full delivery contract and fix loop.