DebugBundle

MCP reference

This route summarizes the shipped MCP surface and links into the generated tool index derived from the implemented tool catalog.

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 open incidents as actionable work. 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: "open".
  2. Filter incidents whose titles show they were intentionally generated for smoke, dogfood, verification, or synthetic checks.
  3. Call resolve_incident for each verified synthetic incident.
  4. Call list_incidents again and confirm the open queue only contains actionable failures.

Open the generated MCP tool reference.

CLI reference

The CLI reference is grounded in the shipped command surface, with the complete command index published under the generated reference subtree.

Webhook reference

The webhook docs now point to a generated event index backed by the shipped webhook contract and schema artifact.

On this page

Incident hygieneSmoke-test cleanup recipe