MCP Distribution

The official DebugBundle MCP server is the local stdio package @debugbundle/mcp, registered as com.debugbundle/mcp in the official MCP Registry.

Use this page to verify that a listing is legitimate before installing it into an agent environment.

Official Channels

The canonical install command is:

npx @debugbundle/mcp

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

For a repository plugin or direct MCP connection, follow the Codex setup guide or Claude Code setup guide. Both cover authentication, verification, updates, and removal.

The separate OAuth-protected endpoint at https://mcp.debugbundle.com/mcp serves the OpenAI Plugin candidate. The Codex and Claude Code developer setups above use the local stdio package; see Remote MCP Status for its current availability.

Marketplace Listings

These downstream listings are discovery surfaces. The official MCP Registry and npm package remain the canonical install sources.

Do not treat a downstream listing as official just because it is searchable. Confirm it points to com.debugbundle/mcp, @debugbundle/mcp, and the debugbundle/debugbundle repository.

Skill And Plugin Channels

DebugBundle also publishes agent instruction and OpenClaw package surfaces:

The portable skill teaches general DebugBundle workflows. A repository-local skill generated by debugbundle setup contains project-specific paths and should take precedence when present.

The Codex and Claude Code plugins bundle local stdio MCP configuration plus a DebugBundle skill. They use the same local CLI auth state or member-token environment flow as the MCP package.

Trust Checks

Before adding DebugBundle MCP to a managed client or marketplace profile, verify:

• Package name is @debugbundle/mcp.
• Official MCP Registry name is com.debugbundle/mcp.
• The source repository is https://github.com/debugbundle/debugbundle.
• Codex developer plugin installs come from the debugbundle repository marketplace.
• Claude Code plugin installs come from debugbundle/debugbundle unless the plugin is later verified in anthropics/claude-plugins-community.
• The public package uses stdio transport. The separately documented OpenAI candidate uses OAuth-protected Streamable HTTP at its production endpoint and remains unavailable as a public ChatGPT listing until review and publication pass.
• Examples use DEBUGBUNDLE_MEMBER_TOKEN or local CLI auth state for MCP operations.
• Examples do not use project tokens for incident retrieval, bundle access, billing, project management, or other MCP management workflows.
• Examples do not contain real member tokens, project tokens, webhook secrets, customer hostnames, or customer bundle data.

Report suspicious listings, leaked examples, or security concerns through the DebugBundle security policy.

Auth Scope

MCP retrieval and management tools use member credentials:

Project tokens are SDK write-only ingestion credentials. They are not valid for MCP management or retrieval.

Remote MCP Status

The general supported public MCP path remains the stdio package. The separate OpenAI Plugin 1.0.0 production endpoint is active at https://mcp.debugbundle.com/mcp for the exact OpenAI OAuth client and exposes twenty-three read-only tools. It includes OAuth/OIDC with PKCE, dedicated no-side-effect readers, tenant authorization, bounded output, rate limits, readiness, reviewer isolation, and same-host operational controls.

The production endpoint has passed Developer Mode connection and bounded client checks, but the plugin has not been submitted, approved, published, or made directory-discoverable. It is therefore not publicly installable. Until those gates pass, other remote-agent environments should run the stdio package in their managed runtime and pass a member token through that runtime's secret mechanism. See OpenAI Plugin for the exact contract and evidence boundaries.

Codex developer integration

The Codex developer plugin bundles the existing stdio server and a workflow skill. Its repository marketplace is .agents/plugins/marketplace.json, and its source package is plugins/debugbundle-codex. Install it from the first-party repository marketplace. This distribution does not imply an approved listing in the OpenAI Plugins Directory.

Codex also supports direct MCP configuration with codex mcp add debugbundle -- npx -y @debugbundle/mcp@1.9.0 --local-auth, including in the IDE extension. Both developer paths use existing CLI/member authentication. The separate hosted OpenAI plugin remains a read-only candidate and is not publicly installable.