Browser Feedback MCP
Related Servers
Alternatives to Browser Feedback MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables visual annotation on web pages for Claude Code, allowing element selection, comment addition, screenshot capture, and structured UI feedback for code fixes via an MCP server.MIT
- AlicenseAqualityDmaintenanceEnables DOM-aware visual annotation of web pages with drawing tools and element selection, submitting structured annotations to Claude Code via MCP for automated feedback processing.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to draw marks and leave numbered notes on a running localhost page in a Chrome window, then send the batch into the active Claude Code session with each note's element, React component, source line, and screenshot. Progress and per-note results stream back onto the page, and the marks persist across navigation, all locally with no cloud.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables drawing annotations directly on local web pages and sending screenshots, DOM data, and annotation context to your IDE agent for precise code edits.49 npm3MIT
- AlicenseNot gradedqualityBmaintenanceLets Claude Code read in-browser review comments, element removals, and text/CSS edits made on localhost dev pages, complete with selectors, HTML, React component names, source files, and screenshots. It also lets the agent claim tasks as in progress and submit solutions for the user to accept or reopen.105 npm1MIT
- AlicenseNot gradedqualityBmaintenanceLets users pin elements on live web pages, describe desired changes, and send those annotations to coding agents. Agents receive the selected targets, notes, screenshots, and source or style context needed to implement the edits.MIT
TDQS
Scored across 12 tools
The retrieval tools overlap heavily: wait_for_browser_feedback, wait_for_multiple_feedback, get_pending_feedback, and preview_pending_feedback all return feedback items and differ mainly in blocking/consuming semantics. Descriptions do clarify the distinctions, but an agent could easily pick the wrong one. The three deprecated widget tools also overlap with each other and with setup_extension.
All tools use consistent snake_case verb_noun form (install_widget, get_pending_feedback, wait_for_multiple_feedback, etc.). The pattern is predictable and readable throughout, with no mixed conventions.
12 tools is reasonable for this scope, though three are marked deprecated, leaving effectively nine active tools. The count is slightly inflated by the legacy widget group that is being phased out in favor of the extension.
The domain (browser feedback collection) is well covered: installation/setup, connection status, multiple feedback retrieval modes, deletion, annotation requests, and browser opening. Coverage is strong, with only minor redundancy from the deprecated-but-retained widget tools.