MCP

BetterBugs MCP (Model Context Protocol) enables you to put your BetterBugs report links directly in AI Agents for AI-assisted RCA and super fast debugging sessions.

BetterBugs MCP: Quick Overview

The BetterBugs MCP (Model Context Protocol) enables you to load BetterBugs bug reports (via report links) directly to your preferred AI Agents and developer environments with MCP Client capabilities (such as Cursor, VS Code, and Windsurf).

Once you configure BetterBugs with your MCP Client, all you need is to paste the BetterBugs bug report link(s) along with your prompt and context to debug it.

The AI Agent then accesses the complete bug report (that comes bundled with the details and technical info, including screenshot, console logs, network requests, events, summary, steps to reproduce, and other info).

The result? You get instant root cause analysis of the issue, possible solutions, and other debugging info and steps.

As a developer, you can use the BetterBugs MCP server AI-debugging combined with your manual skills to resolve software issues significantly faster and better.

PREREQUISITES: What do you need to start using BetterBugs MCP

To start using it, create a bug report using BetterBugs extension and include the report link in your prompt.

Here’re the steps:

Install the BetterBugs Chrome extension.
Take a screenshot of the bug.
Add a title* (required) and description (summary and steps to reproduce) using the “Write with AI Assistant” option .
Hit “Upload Bug Details”.

Your report link is now ready to be consumed by the AI Agent through the MCP Client.

How to configure it for MCP Clients

Visual Studio Code

In your VS Code editor, press CTRL /CMDP + P
Enter >MCP: Add Server
Select HTTP (HTTP or Server-Sent Events)
Enter: https://mcp.betterbugs.io/mcp
Add a name: BetterBugs
Here’s what your mcp.json file should look like:

{
  "servers": {
    "BettterBugs": {
      "url": "https://mcp.betterbugs.io/mcp",
      "type": "http"
    }
  },
  "inputs": []
}

Once you’ve the mcp.json file like above, click the “Start” option available in the json file to authorize BetterBugs with VS Code and start your MCP server.

Cursor

Use the following link to instantly configure Cursor with BetterBugs MCP: -> Add to Cursor

Alternatively, you can configure it manually. Here’re the steps:

Open Cursor and enter CTRL/CMDP + P
Search: >View: Open MCP Settings
In the “Tools and MCP” option from the left navigation panel and click “Add Custom MCP”
Paste the following code in the mcp.json file:

{
    "mcpServers": {
      "BetterBugs": {
        "url": "https://mcp.betterbugs.io/mcp"
      }
    }
}

Save the file and open the “Cursor Settings” tab.
From the “BetterBugs” option, hit “Connect” and then “Open”
Finally, authorize BetterBugs MCP for Cursor

Okay! You’re all set.

Windsurf

Open Windsurf, press CTRL /CMDP + P
Enter: >Windsurf: MCP Marketplace
Click the “Gear Icon” from the right to open the mcp_config.json file.
Add the following code snippet and save:

{"mcpServers": {"BetterBugs": {"url": "https://mcp.betterbugs.io/mcp"}} }

Go back to the MCP Marketplace tab and click the “Reload” icon beside the settings Gear Icon.
Click “open” from the dialogue box and authorize BetterBugs for Windsurf.

Done! You’re all set with the Windsurf configuration with BetterBugs MCP.

Claude Desktop

Open Claude Desktop
From the left pane, open “Settings” and click “Developer”.
In the Local MCP servers window, click “Edit Config”. This opens the system location of the “claude_desktop_config.json” file.
Open the “claude_desktop_config.json” in your text editor.
Paste the following code snippet in the JSON file and save:

{
  "mcpServers": {
    "betterbugs": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.betterbugs.io/mcp",
        "--transport",
        "http-first"
      ]
    }
  }
}

In the Claude app, click the three horizontal lines on the top right and press File > Exit. This correctly applies the changes.
Now, re-open Claude > Settings > Developer

You should see the BetterBugs MCP in the Local MCP servers list.

Here’s another way to check if the BetterBugs MCP is correctly installed with your Claude app.

Open your chat interface in the Claude app.
Click the “Settings” icon (beside the + icon).

You should see Betterbugs there (in the enabled state), ready to go.

Trae IDE

Open the Trae app.
Open the “AI Side Bar” from the top right and click the gear icon for the “AI Management” option
Click the “MCP” tab.
Open the “+ Add” drop down and select “Add Manually”.
Paste the following code snippet in the JSON file and hit “Confirm”.

{
  "mcpServers": {
    "betterbugs": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.betterbugs.io/mcp",
        "--transport",
        "http-first"
      ]
    }
  }
}

Finally, authorize BetterBugs MCP for Trae.

You’re good to go with the BetterBugs MCP config with Trae IDE.

For Other MCP Clients

If you’re using any other MCP clients other than those listed, just add the following code snippet into the mcp JSON file of that client to start using BetterBugs MCP:

{"mcpServers": {"BetterBugs": {"url": "https://mcp.betterbugs.io/mcp"}} }

Getting Started: How to use it

Once you’re good with the config steps, here’s how to use it:

Create a bug report using BetterBugs and copy the report link.
Paste the BetterBugs report link in your MCP client chat space along with the prompt and context for it.
Authenticate the MCP client/IDE with BetterBugs when prompted.
Approve any requests that the AI agent makes to provide more info and context . Continue your debugging session in the chat interface.

BetterBugs MCP: Available tools/properties

Tools/Property Names

Description

getUserDetails

Get authenticated user profile, available workspaces, and account information.

listWorkspaces

Retrieve all workspaces the user has access to, including workspace metadata, permissions, and project counts.

listProjects

List all projects within a specific workspace, including project status, creation dates, and metadata. Requires a workspace_id parameter.

getBugDetails

Fetch comprehensive bug information including title, description, status, priority, reporter, timestamps, and visual evidence (screenshots, screen recordings). Returns structured bug data with metadata.

listBugs

Retrieve all bugs for a specific project, including bug summaries, status, priority, and basic metadata.

getScreenshot

Get a screenshot from the CDN. Requires screenshot_url. Use this to get a screenshot from the CDN. Must be called after getBugDetails. Essential for enhanced visual analysis.

getBugLogs

Get detailed technical logs for a specific bug including console logs, network requests, user interactions, and step-by-step reproduction data.

Prompt Example for using BetterBugs MCP

Prompt

Analyze the following report <BetterBugs Report Link> and provide a RCA for it. Suggest fixes and test cases for the issue. Provide the steps to resolve the issue.

BetterBugs Tools and AI Agent

BetterBugs Report link(bundled with Screenshot and other technical details)
BetterBugs MCP
Cursor

Frequently Asked Question (FAQs)

1 - Can I use more than one BetterBugs report link in my prompt?

Yes. You can use more than one bug report link for analysis and troubleshooting the issue. However, we highly recommend using one report link at a time. This allows your AI agent to perform optimally and cohesively for better context analysis.

2 - Can I use the MCP without BetterBugs Chrome Extension?

Yes. All you need is the BetterBugs report link from any of your team members or end-user who uses the extension for creating BetterBugs reports. Same way, to analyze your own BetterBugs report you’d need the extension to create your reports. Else, you can use report links from others.

No. BetterBugs does not auto-share or analyze your MCP data for training purposes. You can check out our AI privacy policies here.

4 - How do the BetterBugs admins control what MCP can access?

BetterBugs MCP works with the exact permissions set for the BetterBugs report link. The MCP has no access to any data that the user (whom the BetterBugs report belongs to) can’t see already.

PreviousAI Debugger NextBetterBugs Web SDK

Last updated 26 days ago

Was this helpful?