DebugBundle

@debugbundle/mcp

Local artifact safety in 1.19.4

Retained bundle and reproduction paths must stay in their canonical local artifact directories. Unsafe metadata returns invalid_local_artifact_path without reading, rewriting or deleting unrelated files. Symlinked files/directories fail closed. Normal local stores and their existing size allowance are preserved; local state and processing writes use guarded atomic replacement. This supersedes earlier clients.

Cloud cache safety in 1.19.4

Upgrade to 1.19.4 for incident-ID validation before cloud requests and cache writes. Unsafe IDs return invalid_incident_id; UUIDs and existing opaque IDs remain supported. Cloud cache reads, writes and retention reject symbolic links; writes use guarded atomic replacement. This corrects a path traversal present in earlier clients.

Installation guidance in 1.19.4

Prefer one project per system across service repositories, reuse existing connections, and keep separate projects for different access or privacy policies. Inspect existing projects before first-time connect; name matching does not infer system membership.

Local correlation safety in 1.19.1

Trace correlation crosses services only within the same project and environment. If an older cache contains mixed retained source events, reads and incremental processing fail with local_incident_scope_mismatch. Preserve the local store, then explicitly rebuild from its retained event files using debugbundle process --preset with the desired capture preset. This rebuild regenerates local incident/artifact state; it does not change cloud records or the retained event files.

Project/service consolidation 1.19.1

Add logical service context and checked project-merge preview, apply, status, verification, resume and cancellation. Existing identities, credentials and restricted scopes remain compatible. Merge apply requires a qualified compatible core 1.21.0 runtime and remains disabled by default.

Connected doctor diagnostics check API health and saved member authentication with a one-incident probe restricted to cloud_project_id. Missing or blank connected project scope fails before any request. Incident contents are discarded and are not included in the report. Local-only diagnostics make no cloud request.

Connected-workspace incident lists use the saved connection's cloud_project_id unless projectId is explicitly supplied. This also applies to source: "cloud" and every cloud page. An unusable connected project fails with invalid_local_connection_config before the list request; specify the intended project or repair the connection. Local evidence and unconnected account-wide member reads retain their existing behaviour.

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.

Corrective update 1.18.3

Connected incident lists now retain their selected cloud project across all pages, including explicit cloud reads. Invalid connected scope fails before the list request. Tool names, schemas, member authentication and local evidence selection remain compatible. The coordinated OpenClaw plugin repairs native ESM loading and adds installed-host/runtime checks; marketplace security acceptance stays separate.

Install

Ordinary authenticated MCP includes account/project notification preferences, channel-specific pause/resume, and daily email scheduling with local time and IANA timezone. These tools use the same permissions and policies as the API and CLI; the hosted read-only and restricted catalogs remain unchanged. See the tool reference.

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. The separate OpenAI Plugin uses an OAuth-protected read-only remote endpoint at https://mcp.debugbundle.com/mcp. Its review/publication process is independent 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

• Read public project acquisition/activation definitions and aggregate reports with list_analytics_flows and get_analytics_flow_report; owners/admins can manage them with save_analytics_flow and archive_analytics_flow. These developer tools use the same project authorization and flow services as API, CLI and web. The separate hosted OpenAI catalog is unchanged.

• 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.

verify_app_event provides real SDK-driven app proof, matching the CLI's verify cloud --expect-app-event. Pass projectId and at least one of service, traceId, or requestId; environment, maxAgeMinutes, and authFilePath are optional. It reads existing incidents/bundles and never sends synthetic events. The existing verify_cloud schema and description rem