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.
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
Open Cursor Settings, then go to Tools & Integrations (the MCP section).
Choose New MCP Server. Cursor opens your
mcp.jsonfile for editing.Paste the config below and save. Use
~/.cursor/mcp.jsonto enable BugMojo in every project, or.cursor/mcp.jsonat your repo root for one project.Fully quit and reopen Cursor. Return to the MCP settings and check that bugmojo shows a green, connected status.
{
"mcpServers": {
"bugmojo": {
"url": "https://www.bugmojo.com/api/mcp"
}
}
}claude mcp add --transport http bugmojo https://www.bugmojo.com/api/mcpTry 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.
Related articles
- Set up the MCP server in Claude CodeConnect Claude Code to BugMojo over MCP so it can read a bug's replay context, logs, and repro steps and start fixing.
- How AI agents work with BugMojoUnderstand the full loop, from a captured bug to an agent-proposed fix that a human verifies and closes.
- MCP tool referenceKnow exactly which tools a connected AI agent can call over MCP to read a BugMojo bug and act on it.
- Agent access, tokens, and the security modelUnderstand how an AI agent's access is scoped, what it inherits from you, and the guardrails that keep it in bounds.

