DebugBundle
@debugbundle
DebugBundle turns runtime failures, critical-path issues, and availability checks into incidents with full context, alerts, remote probes, and deterministic debug bundles for humans and AI agents.
Overview
What is DebugBundle?
DebugBundle is an MCP server that turns production incidents into deterministic debug bundles for AI agents. It integrates with the DebugBundle platform, allowing agents to inspect incidents, bundles, reproductions, probes, health checks, alerts, webhooks, projects, and setup state via the MCP protocol.
How to use DebugBundle?
Install the server by adding the following configuration to your MCP client, using npx and a DebugBundle member token as the environment variable DEBUGBUNDLE_MEMBER_TOKEN. The server exposes tools for inspection and retrieval of incidents, bundles, health checks, alerts, and project administration.
Key features of DebugBundle
- Incident listing and inspection
- Bundle and reproduction retrieval
- Health checks and probes
- Alerts and webhooks management
- Project, member, token, and billing access
Use cases of DebugBundle
- AI agents debug production incidents by inspecting bundles
- Automate health check monitoring via MCP tools
- Retrieve reproductions and probes for root-cause analysis
- Manage alerts and webhooks programmatically through an agent
FAQ from DebugBundle
What authentication is required?
Use a DebugBundle member token for MCP access by setting the DEBUGBUNDLE_MEMBER_TOKEN environment variable. Do not use a project token for management or retrieval.
Can local users reuse existing CLI authentication?
Yes, the MCP server can reuse existing CLI auth state stored at ~/.debugbundle/auth.json.
What are the runtime dependencies?
The server requires Node.js to run via npx with the package @debugbundle/mcp.
Where can I find more documentation?
Full documentation is available at https://debugbundle.com/docs/mcp.
