How to Integrate BugMojo with Claude Code

What this integration does

BugMojo ships a Model Context Protocol (MCP) server. Add it to Claude Code's MCP config and Claude can list bugs, read bug details with replay context, write comments, and update statuses — all without leaving your IDE. The same MCP server works with Cursor, Windsurf, Cody, and any MCP-compatible client.

The integration is bidirectional where the underlying API supports it — updates flow both directions so neither tool becomes "stale state" relative to the other. For Claude Code specifically, this means during a fix session, claude code reads the bug description + session replay context and proposes a code change.

Before you start

Make sure you have:

• A BugMojo account with admin access (Settings → Integrations is admin-only).
• A Claude Code account with permission to read bugs.
• About 10 minutes of focused time — interruptions during OAuth flows tend to cause re-tries.

Step-by-step setup

Step 1: Generate a BugMojo API key

Settings → API Keys → Create key. Name it claude-code-{your-username}. Copy the key (shown only once; starts with bm_key_).

Step 2: Install the MCP server

Add the server to your Claude Code MCP config (~/.claude/mcp_servers.json or via claude mcp add):

{
  "mcpServers": {
    "bugmojo": {
      "command": "npx",
      "args": ["-y", "@bugmojo/mcp-server"],
      "env": {
        "BUGMOJO_API_KEY": "bm_key_xxx",
        "BUGMOJO_API_URL": "https://bugmojo.com"
      }
    }
  }
}

Step 3: Restart Claude Code

Restart Claude Code or run claude mcp list to confirm the BugMojo server registered. Try the first prompt: 'Show me critical bugs from the past week.'

Workflows this enables

Beyond the "bug appears in Claude Code" basic case, the integration enables several higher-value workflows that justify the setup effort. The most impactful is the first one below — it eliminates ~22 minutes per bug of context-switching according to a 2025 Atlassian study on engineering interrupt costs.

• During a fix session, Claude Code reads the bug description + session replay context and proposes a code change.
• When the fix lands, Claude updates the bug status to 'In Progress' via MCP — no manual context switching.
• Triage flow: ask Claude 'group this week's bugs by suspected root cause' — Claude reads them via MCP and clusters them.

Troubleshooting

"My Claude Code token isn't being accepted." Double-check the token has not expired. Claude Code tokens expire on different schedules depending on token type; regenerate and reconnect if in doubt.

"Bugs aren't appearing in Claude Code."

1. Check Settings → Integrations → Claude Code → Status to confirm the connection is healthy.
2. Verify the target channel is correct.
3. Check Settings → Integrations → Claude Code → Logs for the most recent error.

"Two-way sync is one-way only." Two-way sync depends on the API capability of Claude Code; some integration types (notifications, IDE) are one-way by design.

Privacy and security

For compliance-sensitive teams, the deep-link approach means bug metadata can live in your existing audit-logged Claude Code system while sensitive capture data stays on BugMojo (self-hosted if needed).

Next steps

• Try BugMojo free — no credit card, 5-minute setup.
• Explore other integrations — Slack, Linear, GitHub Issues, Jira, Cursor, Claude Code.
• Read the MCP guide — connect AI coding agents to your bug tracker.