Skip to main content
Glama
mxrcochxvez

bugsmash-mcp

by mxrcochxvez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to bugsmash-mcp

No user-submitted related servers found.

    Related Servers

    • FogBugz

      todevelopers
      A
      license
      A
      quality
      C
      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
      4 npm
      2
      MIT

    • bugsink-mcp

      Nshuti7
      A
      license
      Not graded
      quality
      B
      maintenance
      Hosted MCP server that exposes your self-hosted Bugsink error tracker as tools for LLMs, enabling issue management, release tracking, and stacktrace retrieval via chat prompts.
      584 npm
      MIT

    • greenroom-mcp

      igility
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI coding agents to Greenroom's per-story Storybook reviews, allowing them to list feedback with screenshots, reply to threads, mark stories addressed, and approve stories when explicitly delegated.
      MIT

    • feedback-mcp

      hasna
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources