Skip to main content
Glama

BugSmash MCP

Local Model Context Protocol server that lets an LLM read and manage BugSmash reviewer feedback without ever seeing your BugSmash API key.

LLM (Claude) --MCP--> bugsmash-mcp --HTTPS + X-API-Key--> https://api.bugsmash.io/api/v2

Install

npm install -g @mxrcochxvez/bugsmash-mcp

Or run without a global install via npx (see connector config below).

Requires Node.js 18+.

Related MCP server: Gerrit MCP Server

Generate an API key

  1. Sign in at tools.bugsmash.io.

  2. Open your profile menu → Settings.

  3. Find the API Key section and copy the key.

  4. Treat it like a password. If it leaks, regenerate it immediately from the same settings page.

Official auth docs: docs.bugsmash.io/authentication

Set BUGSMASH_API_KEY (do not commit it)

Export the key in your shell — never put it in a committed file.

export BUGSMASH_API_KEY="your-key-here"

macOS / Linux (zsh), persist for your user:

echo 'export BUGSMASH_API_KEY="your-key-here"' >> ~/.zshrc
source ~/.zshrc

Confirm it is set (does not print the value):

test -n "$BUGSMASH_API_KEY" && echo "BUGSMASH_API_KEY is set"

Register as a user-level MCP connector

Use a user scope so the server is available in every project.

claude mcp add --scope user bugsmash --env BUGSMASH_API_KEY=$BUGSMASH_API_KEY -- npx -y @mxrcochxvez/bugsmash-mcp

If you installed globally:

claude mcp add --scope user bugsmash --env BUGSMASH_API_KEY=$BUGSMASH_API_KEY -- bugsmash-mcp

Claude Desktop

Edit your Claude Desktop config (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "bugsmash": {
      "command": "npx",
      "args": ["-y", "@mxrcochxvez/bugsmash-mcp"],
      "env": {
        "BUGSMASH_API_KEY": "your-key-here"
      }
    }
  }
}

Prefer injecting the key from the environment your Desktop app inherits, rather than pasting it into a synced config file when possible.

Cursor

Add a similar MCP entry: command npx, args ["-y", "@mxrcochxvez/bugsmash-mcp"], and BUGSMASH_API_KEY under env.

Tools

Tool

BugSmash API

Purpose

list_projects

GET /projects

Paginated project list (find projectId)

get_project

GET /project/{projectId}

Project details + versions

list_feedback

GET /comments?projectId

All reviewer comments on a project

get_feedback

GET /comment/{commentId}

Single comment (+ replies)

update_feedback

PATCH /comment/{commentId}

Update text / status / priority / privacy

list_replies

GET /comment/{commentId}/replies

Thread replies

post_reply

POST /reply

Reply on a thread

Base URL: https://api.bugsmash.io/api/v2
Auth header: X-API-Key (never a tool argument).

Typical flow: list_projects → list_feedback → optionally update_feedback / post_reply.

Security note

  • The API key is read only from BUGSMASH_API_KEY.

  • It is never accepted as a tool parameter.

  • It must never be logged, printed, masked-partially in errors, or returned in tool responses.

  • On startup, a missing key exits with the generic message BUGSMASH_API_KEY is not set.

  • All HTTP calls go through one helper that attaches X-API-Key; request headers are not surfaced on errors.

Local development

git clone https://github.com/mxrcochxvez/bugsmash_mcp.git
cd bugsmash_mcp
npm install
npm run build
export BUGSMASH_API_KEY="your-key-here"
npm start
npm run typecheck   # tsc --noEmit
npm run pack:check  # preview files included in the npm tarball

API reference: docs.bugsmash.io

Available Tools

7 tools
get_feedbackGet BugSmash commentA

Fetch a single comment by UUID, including replies when present. Maps to GET /comment/{commentId}.

Inputs: commentId (required), plainText, locationMetadata.

get_projectGet BugSmash projectA

Fetch details for a single BugSmash project, including versions and review links. Maps to GET /project/{projectId}.

Inputs: projectId (required).

list_feedbackList BugSmash feedbackA

Retrieve all reviewer comments for a project. Maps to GET /comments?projectId. Prefer plainText=true for LLM consumption. Optionally include location metadata (pin/DOM/page).

Inputs: projectId (required), status, plainText, locationMetadata.

list_projectsList BugSmash projectsA

List review projects in the BugSmash workspace (paginated). Use this to discover project IDs before calling list_feedback. Maps to GET /projects.

Inputs: page, limit, types, folderId.

list_repliesList comment repliesA

List all replies on a comment thread. Maps to GET /comment/{commentId}/replies.

Inputs: commentId (required), plainText.

post_replyReply to a BugSmash commentB

Post a reply on an existing comment thread. Maps to POST /reply.

Inputs: text (required), commentId (required), isPrivate.

update_feedbackUpdate BugSmash commentA

Update a comment's text, status (e.g. mark Resolved), priority, or privacy. Maps to PATCH /comment/{commentId}. At least one field besides commentId is required.

Inputs: commentId (required), text, status, priority, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: projects vs comments vs replies, and list/get vs update/post. No two tools overlap in purpose, making selection unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_projects, get_project, get_feedback, list_feedback, update_feedback, list_replies, post_reply), with no stylistic deviations.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose. Each tool is necessary and non-redundant, covering project discovery, feedback retrieval/update, and reply management.

    Completeness5/5

    The tool set provides complete coverage for the domain: discover projects, fetch project details, list/get feedback, update feedback, and manage reply threads. No critical operations are missing for the intended workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A MCP server for interacting with FogBugz issue tracker through LLMs such as Claude. Supports both the XML API (/api.asp) and the JSON API (/f/api/0/jsonapi) with automatic version detection at startup. Works with on-premise and on-demand FogBugz installations.
      19
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Open Feedback, enabling AI assistants to submit, list, get, update status of, and analyze product feedback via a local HTTP API and JSONL storage.
      346 npm
      Apache 2.0