@debugbundle/mcp

MCP server for runtime error reporting, crash reporting, incident response, endpoint health checks, debug bundles, and product analytics. DebugBundle lets agents inspect customer-facing incidents, deterministic bundles, product-usage evidence, reproductions, probes, alerts, webhooks, projects, and setup state through the same management surface as the API and CLI. It is production debugging infrastructure, not a generic infrastructure-monitoring or observability platform.

Install

Run the stdio server directly with npm:

npx @debugbundle/mcp

Or install globally:

npm install -g @debugbundle/mcp
debugbundle-mcp

Supported Node.js versions: 22.x through 26.x.

MCP Client Config

{
  "mcpServers": {
    "debugbundle": {
      "command": "npx",
      "args": ["@debugbundle/mcp"]
    }
  }
}

Use npx -y @debugbundle/mcp in clients that require noninteractive package execution.

Install Matrix

This package is the supported public local stdio path. A separate OpenAI Plugin 1.0.0 source candidate targets an OAuth-protected read-only remote endpoint at https://mcp.debugbundle.com/mcp; it is not deployed, submitted, published, or publicly installable yet and does not alter this package's catalog or authentication.

Local authentication profile

MCP 1.9.0 adds npx @debugbundle/mcp --local-auth. This opt-in profile removes bearerToken from tool schemas, rejects per-call credentials and unknown fields, and uses only the server's startup CLI/environment member authentication. Hosted tools that require a member token fail with mcp_tool_error:auth_state_missing before an API request when auth is absent; run debugbundle login on that host or configure the server environment and restart the connection. Local-only retrieval remains available without a token. The default invocation preserves the legacy schemas and explicit per-tool token precedence.

Codex

Codex can use the existing stdio server independently of the hosted OpenAI plugin. See the Codex developer package and Codex setup guide for the repository marketplace, direct configuration, authentication, verification, and removal. The repository plugin must be released on the default branch before GitHub installation works; local checkout installation is available for candidate validation.

Claude Desktop

In Claude Desktop, open Settings > Developer, edit the local MCP config, and add:

{
  "mcpServers": {
    "debugbundle": {
      "command": "npx",
      "args": ["-y", "@debugbundle/mcp"]
    }
  }
}

Run debugbundle login first to reuse local CLI auth state, or add DEBUGBUNDLE_MEMBER_TOKEN to the server environment for managed/headless use. Set DEBUGBUNDLE_API_URL only for self-hosted or non-default API hosts.

Claude Code Plugin

Claude Code users can add DebugBundle's first-party marketplace from this repository:

/plugin marketplace add debugbundle/debugbundle
/plugin install debugbundle@debugbundle

The plugin package lives at apps/mcp/claude-code/debugbundle and bundles a Claude Code skill. See the Claude Code setup guide for the plugin's pinned MCP version, direct MCP configuration, authentication, verification, updates, and removal. It is also structured for Claude community marketplace review; do not describe it as listed in claude-community until Anthropic accepts and publishes it.

Authentication

What Agents Can Do

• List active incidents and fetch full incident context.
• Fetch deterministic debug bundles and reproduction artifacts.
• Query aggregate usage, routes, device/browser/OS/language segments, referrers, actions, funnels, and journey patterns without waiting for an analysis artifact through get_usage_summary, get_route_metrics, get_device_breakdown, get_action_metrics, get_funnel_analysis, and related reads.
• Inspect retained redacted journey samples, analytics opportunities, and generated AnalyticsBundles; request a bounded analysis artifact when aggregate metrics alone are insufficient.
• Read analytics settings before proposing privacy, retention, consent, capture, or approved custom-dimension changes; update them only with explicit owner/admin intent.
• List saved analytics funnels and, with owner/admin access, create, update, or archive reusable funnel definitions through list_saved_analytics_funnels, create_saved_analytics_funnel, update_saved_analytics_funnel, and archive_saved_analytics_funnel.
• Inspect hosted health checks, probes, alerts, webhooks, projects, members, billing, capture policy, and GitHub automation state.
• Run local and hosted verification through tools such as verify_local, verify_cloud, doctor, smoke, and analyze.
• Resolve or reopen incidents after verification.

For analytics questions, use direct aggregate tools first and generate an AnalyticsBundle only when a bounded analysis needs a durable artifact. The product does not create one bundle per visit.

Troubleshooting

Links

• Docs: https://debugbundle.com/docs/mcp
• Agent workflows: https://debugbundle.com/docs/agent-workflows
• LLM index: https://debugbundle.com/llms.txt
• MCP tool schema: https://debugbundle.com/schemas/mcp-tools.json
• OpenAI Plugin candidate: https://debugbundle.com/docs/mcp/openai-plugin
• Official MCP Registry metadata: https://github.com/debugbundle/debugbundle/blob/main/apps/mcp/server.json

Security And Trust

• Official MCP Registry name: com.debugbundle/mcp.
• Official npm package: @debugbundle/mcp.
• Source repository: https://github.com/debugbundle/debugbundle/tree/main/apps/mcp
• License: Apache-2.0.
• The server uses stdio transport and local process credentials. It does not include hidden hosted management auth.
• Public examples must use placeholders only; never paste real member tokens, project tokens, webhook secrets, or customer configuration into marketplace listings.

License

Apache-2.0.