The Context Switch That Breaks Your Flow

You're deep in the code, tracing a bug through three layers of abstraction, and then it happens — a Slack message arrives: "Bug #47 is still broken." Now you have to open a browser, navigate to the Bugoon dashboard, find the report, read the screenshot, copy the stack trace, and paste it back into your editor. By the time you're back in your IDE, the mental model you spent 20 minutes building is gone.

Context switching between your editor and a bug dashboard is one of the most disruptive rhythms in a developer's day. We built the Bugoon MCP Server to eliminate it entirely.

What You Can Do with the Bugoon MCP Server

The Bugoon MCP Server brings your bug reports directly into Claude Code, Cursor, and any other MCP-compatible editor. No tab switching. No copy-pasting. Just bug data, exactly where you're already working.

It ships with five Tools and two Prompts:

Tools

list_bug_reports — Fetch all bug reports for a project, with optional filtering by status. Get a quick overview without leaving your editor.
get_bug_report — Retrieve the full details of a specific report: description, reproduction steps, browser metadata, and annotated screenshot path.
get_screenshot — Pull the screenshot attached to a bug report directly into your AI conversation, so the model can see exactly what the user saw.
update_bug_report_status — Mark a bug as in_progress, resolved, or closed without ever opening the dashboard.
get_project — Retrieve project-level metadata, including your API key configuration and project settings.

Prompts

fix_bug — A structured prompt that loads a bug report and its screenshot, then asks the AI to propose a fix with reasoning. Great for kicking off a focused fix session.
triage_bug — A prompt that evaluates a bug report and suggests a priority level and next action, helping teams stay on top of incoming reports.

Quick Start in 30 Seconds

Add a .mcp.json file to the root of your project with the following configuration:

{
  "mcpServers": {
    "bugoon": {
      "command": "npx",
      "args": ["-y", "@rubyjobs-jp/bugoon-mcp-server"],
      "env": {
        "BUGOON_SECRET_KEY": "YOUR_SECRET_KEY",
        "BUGOON_API_URL": "https://bugoon.com"
      }
    }
  }
}

Replace YOUR_SECRET_KEY with the secret key from your Bugoon project settings. That's it — no global installs, no daemon processes. npx handles the rest on first use.

Once the file is in place, restart your editor and the Bugoon tools will appear automatically in your MCP tool list.

Supported Editors

The Bugoon MCP Server works with any editor that supports the Model Context Protocol:

Claude Code — Full support for Tools and Prompts. Use fix_bug to jump straight into an AI-assisted fix session from the terminal.
Cursor — Add .mcp.json to your project root and access Bugoon tools through Cursor's MCP integration panel.
Other MCP-compatible editors — Any editor that implements the MCP specification can load the Bugoon server using the same .mcp.json configuration.

Because the configuration lives in .mcp.json at the project root, the setup is portable and version-controllable. Commit it to your repo (with the secret key in a .env file or CI secret, not hardcoded) and every team member gets the same experience.

Next Steps

Ready to set it up end-to-end in under five minutes? We've put together a step-by-step tutorial that covers creating a project, generating your secret key, configuring .mcp.json, and running your first fix_bug prompt.

Check out the full setup guide on the Bugoon blog: bugoon.com/ja/blog/

If you haven't signed up yet, get started for free and grab your secret key in minutes.

Try Bugoon for free

Introducing Bugoon MCP Server: Access Bug Reports Directly from Claude Code and Cursor