A
licenseNot graded
qualityA
maintenanceEnables 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
feedbug-mcp
Related Servers
Alternatives to feedbug-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceFeedback ingestion for AI agents. Record your screen and talk; your agent does the rest — files the bugs, writes the spec, builds the backlog.930MIT
- AlicenseAqualityFmaintenanceUnleashes 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.21,238Apache 2.0
- AlicenseNot gradedqualityDmaintenanceStreams browser DevTools console, network, storage, and performance data to your IDE's AI agent for real-time debugging and analysis.8 npm1MIT
- AlicenseAqualityBmaintenanceEnables blind AI coding models to debug visual bugs by capturing screenshots, analyzing them with a vision-capable model, and returning a written report.15MIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to discover, understand, and fix product issues (UX inconsistencies, accessibility violations, quality problems) identified by Skippr's browser extension through natural language commands.1118 npmMIT
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
ActivitySlowing
ResponsivenessNo issues