bugsmash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUGSMASH_API_KEY | Yes | Your BugSmash API key. Generate it at tools.bugsmash.io. Treat it like a password. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List review projects in the BugSmash workspace (paginated). Use this to discover project IDs before calling list_feedback. Maps to GET /projects. |
| get_projectA | Fetch details for a single BugSmash project, including versions and review links. Maps to GET /project/{projectId}. |
| list_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). |
| get_feedbackA | Fetch a single comment by UUID, including replies when present. Maps to GET /comment/{commentId}. |
| update_feedbackA | 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. |
| list_repliesA | List all replies on a comment thread. Maps to GET /comment/{commentId}/replies. |
| post_replyB | Post a reply on an existing comment thread. Maps to POST /reply. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.