BugMojo

@bugmojo/mcp-server

MCP server that connects AI coding agents — Claude Code, Cursor, VS Code, Claude Desktop — to BugMojo bug tracking.

Why

BugMojo captures pixel-perfect bug reports straight from the browser — session replay, console logs, network requests, screenshots. This MCP server hands that context to your AI coding agent: it can list, search, and read bugs, file new ones, update status/priority/assignee, and add comments over BugMojo's API-key-authenticated REST API. Your agent fixes bugs with the full capture context instead of a one-line description.

Want the full surface? Regression suites/runs, testing workflow, agents, session-replay summaries, and inline console/network logs are available on the hosted, OAuth-authenticated HTTP endpoint at https://www.bugmojo.com/api/mcp — see Full surface (OAuth HTTP) below. This npm package intentionally stays a minimal bugs shim so every tool maps to a real endpoint (nothing 404s).

Install

Requires Node.js 18+. No install needed — MCP clients run it with npx:

npx -y @bugmojo/mcp-server

Or install the bugmojo-mcp command globally:

npm install -g @bugmojo/mcp-server

or

pnpm add -g @bugmojo/mcp-server

or

yarn global add @bugmojo/mcp-server

It speaks MCP over stdio and reads two environment variables (below).

Quickstart (Claude Code, 60 seconds)

1. Generate an API key in your BugMojo dashboard under Settings → API Keys (it starts with bm_key_).
2. Register the server:

claude mcp add bugmojo -e BUGMOJO_API_KEY=bm_key_your_key_here -- npx -y @bugmojo/mcp-server

1. Ask Claude: *"List the open CRITICAL bugs and summarise the newest one."*

Configuration

Client setup

Claude Code

Either use the CLI (per-user):

claude mcp add bugmojo -e BUGMOJO_API_KEY=bm_key_your_key_here -- npx -y @bugmojo/mcp-server

Or check a project-scoped .mcp.json into your repo root so the whole team gets it:

{

"mcpServers": { "bugmojo": { "command": "npx", "args": ["-y", "@bugmojo/mcp-server"], "env": { "BUGMOJO_API_KEY": "bm_key_your_key_here" } } } }

Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{

"mcpServers": { "bugmojo": { "command": "npx", "args": ["-y", "@bugmojo/mcp-server"], "env": { "BUGMOJO_API_KEY": "bm_key_your_key_here" } } } }

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{

"mcpServers": { "bugmojo": { "command": "npx", "args": ["-y", "@bugmojo/mcp-server"], "env": { "BUGMOJO_API_KEY": "bm_key_your_key_here" } } } }

VS Code (MCP)

.vscode/mcp.json:

{

"servers": { "bugmojo": { "command": "npx", "args": ["-y", "@bugmojo/mcp-server"], "env": { "BUGMOJO_API_KEY": "bm_key_your_key_here" } } } }

Any other MCP client

Point it at the same stdio command: npx -y @bugmojo/mcp-server (or bugmojo-mcp if installed globally) with BUGMOJO_API_KEY in the environment. Add BUGMOJO_API_URL only if you self-host.

Tools

That's the whole npm package — six tools, each mapping to a real /api/v1/bugs/* endpoint.

Full surface (OAuth HTTP)

Regression suites/runs, the testing (QA) workflow, agents, session-replay summaries (summarize_replay), and inline console/network logs (get_bug_console_logs, get_bug_network_logs) are served by the hosted, OAuth 2.1-authenticated streaming endpoint — not this npm package. Point an HTTP-capable MCP client at:

https://www.bugmojo.com/api/mcp

The client opens a browser login the first time (no API key to manage). Optional query params: ?workspace= binds the connection to a workspace, and ?mode=admin additionally exposes the admin-management tools.

// Claude Code / clients that support remote MCP servers

{ "mcpServers": { "bugmojo": { "type": "http", "url": "https://www.bugmojo.com/api/mcp" } } }

Example

Once configured, ask your agent things like:

"List the open CRITICAL bugs in project X, open the newest one, and summarise the repro steps."

The agent calls list_bugs (status=OPEN, priority=CRITICAL), then get_bug for the full context — including the session replay BugMojo captured in the browser.

How it works

This package is a thin, stateless client: it translates MCP tool calls into authenticated HTTPS requests to the BugMojo REST API (/api/v1). All business logic and data live in your BugMojo instance — nothing is stored locally.

Troubleshooting

"BUGMOJO_API_KEY environment variable is required" The key isn't reaching the server process. Put it in the env block of your MCP config (or pass -e BUGMOJO_API_KEY=... to claude mcp add) — shell exports are not inherited by every MCP client.

"BUGMOJO_API_KEY must start with 'bm_key_' prefix" You copied the wrong value (e.g. a session token or a truncated key). Regenerate the key in the dashboard under Settings → API Keys and copy the whole bm_key_... string.

"Authentication failed ... Check your BUGMOJO_API_KEY" (401) The key was revoked or belongs to a different instance. Generate a fresh key; if you self-host, also confirm BUGMOJO_API_URL points at that instance.

"Permission denied" (403) on create/update/comment Your key is read-only. create_bug, update_bug, and add_comment need a write-scoped key.

"fetch failed" / ECONNREFUSED The server can't reach BUGMOJO_API_URL. The default is https://www.bugmojo.com; if you set a self-hosted/local URL, make sure that instance is running and reachable.

Server disconnects immediately on first run Make sure your config uses "args": ["-y", "@bugmojo/mcp-server"] — without -y, npx's first-run "Ok to proceed?" prompt hangs the stdio handshake. Also confirm node --version is 18 or newer.

Related packages

Links

• Website — https://www.bugmojo.com
• Docs & issues (GitHub) — https://github.com/viveksinra/bugmojo-sdk
• Issues — https://github.com/viveksinra/bugmojo-sdk/issues
• Changelog — https://github.com/viveksinra/bugmojo-sdk/blob/main/packages/mcp-server/CHANGELOG.md
• Model Context Protocol — https://modelcontextprotocol.io

License

MIT © Softech Infra