BugMojoBugMojo
Get started
How-to

Install BugMojo in Cursor

One click from the install deeplink, or a four-line mcp.json — plus a rule that only loads when you are in test code.

Applies toPlans:FreeProBusinessEnterpriseRoles:OwnerAdminDeveloperQaWhere:MCP

One click

text
cursor://anysphere.cursor-deeplink/mcp/install?name=bugmojo&config=eyJ1cmwiOiJodHRwczovL3d3dy5idWdtb2pvLmNvbS9hcGkvbWNwP21vZGU9cWEifQ%3D%3D

The link installs the hosted endpoint with the QA tool surface. Cursor then prompts for the browser login on the first tool call.

Or by hand

  1. Open Cursor Settings → Tools & Integrations and choose New MCP Server.

  2. Paste the config below. Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json at your repo root for one project.

  3. Fully quit and reopen Cursor.

  4. Return to MCP settings. When the server shows Needs login, choose Authorize and complete the browser prompt. It should end green and connected.

.cursor/mcp.json
{
  "mcpServers": {
    "bugmojo": {
      "url": "https://www.bugmojo.com/api/mcp?mode=qa"
    }
  }
}

What the plugin adds

PartWhat it does
mcp.jsonOne server: the hosted endpoint, OAuth in the browser.
rules/bugmojo.mdcA rule globbed to tests/**, e2e/** and playwright.config.*. It enters context only when you are in test code.
skills/The same skills the Claude Code plugin ships — plan, generate, run, assign, report, fix a bug, triage.

The rule teaches Cursor how to annotate a spec so a result maps to a test case, and which flakiness patterns to avoid — unordered-collection assertions, hard waits, missing assertions, network-timing assumptions.

Troubleshooting

  • The server stays red or does not appear
    Likely cause: Cursor was not fully restarted, or the URL has a typo.
    Quit Cursor entirely (not just the window), reopen, and confirm the URL is exactly https://www.bugmojo.com/api/mcp with any query string after it.
  • The deeplink opens Cursor and installs nothing
    Likely cause: The base64 payload encodes the wrong object.
    The payload must be the server object — {"url":"…"} — not the whole mcpServers map. Generate the link rather than hand-encoding it.
  • Tools are missing that you expected
    Likely cause: Your role lacks the permission, or the mode switch is not set.
    Call whoami to see your role and permissions, or reconnect with ?mode=all.
  • The rule never fires
    Likely cause: You are not editing a file it globs.
    It is deliberately scoped to test files. Open something under tests/ or e2e/, or ask about the conventions directly.

Common questions

Which Cursor version do I need?

3.13.0 or later — the plugin manifest declares that as its minimum client version.

Why is the rule not always on?

It is globbed to <code>tests/**</code>, <code>e2e/**</code> and <code>playwright.config.*</code>. A rule that loads on every request is a tax on every request.

The deeplink opened Cursor but installed nothing.

The base64 payload must be the server object alone. Generate the link with the plugin's deeplink script rather than hand-encoding it.

How is this different from just adding the MCP server?

The MCP server gives Cursor the tools. The plugin adds the rule and the shared skills — planning, generating, running, assigning and reporting.

Was this helpful?
Updated Sep 19, 2026 · Still stuck? Contact support

Related articles