loupe-mcp
Related Servers
Alternatives to loupe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceServes coding agents the annotations users leave on elements of a running dev app, including the element selector, DOM context, component name and exact source file:line. Agents can list and watch for pending feedback, link a page to their repository, and acknowledge, reply to, resolve or dismiss each annotation so the thread resolves on the page.MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceBridges UI feedback captured by a browser extension on localhost apps into a Claude Code session, queueing picked elements, comments and rewrite requests as batches that the coding agent can claim and act on. It also lets Claude report progress and per-item results back to the extension, and can import batches exported as JSON.MIT

Commentifyofficial
AlicenseNot gradedqualityBmaintenanceEnables Claude to search your team's design and issue comment threads from Figma, Jira, and Notion, answer questions with citations, surface feedback relevant to the code you're editing, and post replies or close threads after your confirmation.MIT- AlicenseAqualityCmaintenanceEnables visual browser feedback collection directly into Claude Code. Users can point at elements in their browser and send annotated feedback that Claude can act on immediately.121MIT

layerdock-mcpofficial
AlicenseAqualityCmaintenanceRead 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.56 npmMIT
TDQS
Scored across 19 tools
Most tools target distinct resources or actions, but there is some overlap among the context-gathering tools: get_element_context, get_comment, get_latest_selection, and find_source_for_selection can all return element or source context. The detailed descriptions help clarify when to use each, though an agent could still hesitate between get_comment and get_element_context with a thread_id.
All tool names use snake_case and begin with a verb (get_, list_, update_, add_, create_, etc.), following a predictable verb_noun pattern. Minor variations like prepositions or abbreviations (create_pr_for_thread) are still consistent and readable.
With 19 tools, the set is slightly heavy for a single server, but it covers several distinct domains: agent activity monitoring, companion messaging, feedback thread management, element selection, and PR creation. Each tool appears to earn its place, though the count is at the upper edge of what feels well-scoped.
The tools cover core workflows for activity tracking, companion chat, comment/thread interaction, element context retrieval, change proposals, and PR creation. A few gaps exist, such as creating or deleting comments directly and searching/filtering comments, but agents can work around these in most scenarios.