mcpdirectory.dev
9,129 servers · updated 23 Sept

Debugbundle MCP server

official from Debugbundle Active last commit 18 d
{
  "mcpServers": {
    "debugbundle": {
      "command": "npx",
      "args": [
        "-y",
        "@debugbundle/mcp@latest"
      ],
      "env": {
        "DEBUGBUNDLE_MEMBER_TOKEN": "<debugbundle_member_token>",
        "DEBUGBUNDLE_PROBE_TRIGGER_SECRET": "<debugbundle_probe_trigger_secret>",
        "ANALYTICS_HASH_SECRET": "<analytics_hash_secret>",
        "DEBUGBUNDLE_PROJECT_TOKEN": "<debugbundle_project_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @debugbundle/mcpversion 1.10.0

What it does

DebugBundle is an MCP server that exposes runtime error reporting, incident management, health checks, and product analytics for production applications. It helps developers and AI agents access structured debugging bundles containing errors, logs, traces, and context from production incidents.

  • Query production incidents and retrieve detailed debug bundles containing error context, logs, and deployment metadata.
  • Monitor endpoint health and trigger alerts based on customer-facing runtime failures.
  • Analyze product usage patterns and funnel performance through generated AnalyticsBundles without storing raw event data long-term.

Tools this server exposes

ToolDoes
incidentsList and query production incidents from local or cloud sources.
inspectRetrieve detailed debug bundle contents for a specific incident.
health_checkCheck endpoint health status and availability.
analyticsQuery product usage metrics, routes, funnels, and friction markers.
projectsManage DebugBundle projects and configuration.
webhooksSet up or manage incident notification webhooks.
alertsCreate and manage incident alerts.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.