DebugBundle
Reference

MCP v1 surface summary

Versioned summary of the shipped DebugBundle MCP surface. Use the main MCP guide for setup, authentication, and workflow details.

Primary MCP guide

For installation, authentication, and agent workflow setup, start with MCP Server. This page is a versioned summary route for the v1 docs tree.

Setup and validation

Tools cover the same setup, doctor, validate, verify, and smoke paths exposed through the CLI.

Retrieval and artifacts

Incidents, bundles, reproductions, and logs all remain available through the MCP surface.

Management parity

Tokens, alerts, webhooks, weekly reports, and project flows stay aligned with the API and CLI surfaces.

Incident hygiene

Treat active incidents as actionable work. Active means open or regressed. After a fix is verified, or after an intentional smoke, dogfood, or verification incident has served its purpose, resolve it through MCP so agents and humans see the same remaining queue.

Smoke-test cleanup recipe

  1. Call list_incidents with status: "active".
  2. Filter incidents whose titles show they were intentionally generated for smoke, dogfood, verification, or synthetic checks.
  3. Call resolve_incidents for verified synthetic incidents, or resolve_incident for a single incident.
  4. Call list_incidents again and confirm the needs-attention queue only contains actionable failures.

Open the generated MCP tool reference.

On this page