Schema | bugsmash-mcp

bugsmash-mcp

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.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mxrcochxvez/bugsmash_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server