Skip to main content
Glama
Sign In
feedbug-mcp

feedbug-mcp

by joffreyBerrier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to feedbug-mcp

No user-submitted related servers found.

    Related Servers

    • bugsnap-mcp

      akusaradigital
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to inspect annotated screenshots, user action steps, console errors, and failed network requests from bug reports, with tools, resources, and prompts for diagnosis and triage.
      2
      MIT
    • layerdock-mcp

      layerdock-mcpofficial

      LayerDock
      A
      license
      A
      quality
      C
      maintenance
      Read Layerdock website feedback in your coding agent. Each pin comes with the CSS selector, screenshot, page URL and the console and network trace captured when the client reported it. Fix the bug, reply on the thread and mark it resolved without leaving the editor. Works with Claude Code, Cursor, Codex CLI, Windsurf, VS Code, Zed and Antigravity.
      5
      11 npm
      MIT
    • uigrep

      uigrepofficial

      SalzDevs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to pull structured UI feedback captured in the browser — including element selectors, bounding boxes, computed styles, screenshots, and annotations — and to mark issues as fixed.
      MIT
    • WebEvalAgent MCP Server

      WebEvalAgent MCP Serverofficial

      refreshdotdev
      A
      license
      A
      quality
      F
      maintenance
      Unleashes LLM-powered agents to autonomously execute and debug web apps directly in your code editor, with features like webapp navigation, network traffic capture, and console error collection.
      2
      1,232
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a clearly named purpose, and the list/get distinction plus the specialized context getters are explicit. The only real overlap is that feedbug_get_bug returns replay URLs, diagnostics, and DOM context that also have dedicated getters, but the descriptions directly call out when to use the subsets instead.

    Naming Consistency5/5

    All tools share the consistent feedbug_ prefix and follow a clear verb_noun pattern: list_bugs, get_bug, get_html_context, get_diagnostics, get_replay, add_comment, resolve_bug. The naming is predictable and makes the toolset easy to navigate.

    Tool Count5/5

    Seven tools is well-scoped for a bug-reporting server. Each tool covers a distinct retrieval path or action without redundancy, and there is no padding or unnecessary surface area.

    Completeness4/5

    The server covers the core bug-report workflow: list, inspect in full, drill into DOM/browser/replay, comment, and resolve. Minor gaps exist—there is no reopen, update, or comment listing—but the descriptions acknowledge these limitations and the tracker remains the source of truth for broader lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources