How-to

Set up the BugMojo MCP server in Cursor

Connect Cursor to BugMojo over MCP so its AI can read a bug's replay, logs, and repro steps.

Applies toPlans:FreeProBusinessEnterpriseRoles:OwnerAdminDeveloperWhere:MCP

Cursor can connect to BugMojo through the Model Context Protocol (MCP). Once connected, Cursor's AI can pull a bug's session replay context, console logs, network requests, and repro steps straight into your editor, so you fix the real problem without leaving your code.

What you need

You need Cursor installed with MCP support (recent versions include it), a BugMojo account, and at least one captured bug to test against. No API key is required for the hosted endpoint below.

Add BugMojo in Cursor

  1. Open Cursor Settings, then go to Tools & Integrations (the MCP section).

  2. Choose New MCP Server. Cursor opens your mcp.json file for editing.

  3. Paste the config below and save. Use ~/.cursor/mcp.json to enable BugMojo in every project, or .cursor/mcp.json at your repo root for one project.

  4. Fully quit and reopen Cursor. Return to the MCP settings and check that bugmojo shows a green, connected status.

~/.cursor/mcp.json
{
  "mcpServers": {
    "bugmojo": {
      "url": "https://www.bugmojo.com/api/mcp"
    }
  }
}
Terminal
claude mcp add --transport http bugmojo https://www.bugmojo.com/api/mcp

Try it

In Cursor's chat, reference a bug by its ID or paste its BugMojo link and ask a question such as "What broke in this bug?". Cursor calls the BugMojo tools, reads the replay context and logs, and suggests a fix grounded in what really happened. See the MCP tool reference for every tool it can call.

Common questions

Where does Cursor store the MCP config?

In an <code>mcp.json</code> file. Use <code>~/.cursor/mcp.json</code> for every project, or a <code>.cursor/mcp.json</code> at your repo root for a single project.

Why doesn't BugMojo show up in Cursor's tools?

Fully quit and reopen Cursor after editing mcp.json, then open Settings and check that the bugmojo server shows a green, connected status.

Which bug does the agent read?

Ask Cursor about a specific bug by its ID or paste the bug link. The MCP server returns that bug's replay context, console and network logs, and repro steps.

Was this helpful?
Updated Jul 10, 2026 · Still stuck? Contact support

Related articles