A
licenseA
qualityD
maintenanceVisual feedback as agent work packets: stakeholders pin on your live app and your AI coding agent reads each pin (selector, screenshot, DOM, thread, acceptance criteria) via MCP and ships the fix.
39
1,340 npm
1
MIT
loopback
Related Servers
Alternatives to loopback
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to pull, triage, and resolve user feedback pinned directly on live web prototypes via MCP tools.46 npm2MIT
- FlicenseNot gradedqualityAmaintenanceEnables UI feedback loop by clicking elements, leaving comments, and letting AI coding agents (via MCP) resolve annotations interactively.2-
- FlicenseNot gradedqualityCmaintenanceHuman-to-AI code review bridge. Annotate UI elements in the browser with review comments, and AI agents read the feedback via MCP to fix code automatically — with full element context (CSS selector, styles, DOM path, accessibility info). 10 MCP tools, framework-agnostic Web Component, zero-config install via uvx.9-
- AlicenseNot gradedqualityDmaintenanceMCP server for visual feedback, video direction, and QA assertions on web pages, enabling AI agents to read, reply, and resolve annotations in real time.6MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for collecting and resolving website feedback via AI; reviewers click elements and type requests, then AI agents pull fix prompts and resolve notes automatically.1MIT
TDQS
A4.4/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct action in the feedback lifecycle—create, read, list, claim, correct, comment, link, status transition, and final resolution—so there is no real overlap. The closest pair (update_feedback vs update_status) is explicitly disambiguated by naming the report fields vs workflow state.
Naming Consistency5/5
All tools follow the loopback_<verb>_<object> pattern with snake_case throughout. The object noun changes predictably with the action (submit/get/list/claim/resolve on feedback, get on stats, update on status).
Tool Count5/5
Ten tools cover the complete feedback queue workflow without redundancy or bloat. Each tool earns its place: submission, triage, claiming, status changes, audit comments, fix linking, and stats.
Completeness5/5
The tool surface supports the full lifecycle from filing feedback through investigation, fix linkage, status transitions, and verified/wontfix closure. No significant missing operation remains because resolve provides a terminal state and update_feedback corrects inaccurate reports.
Maintenance
ActivitySlowing
ResponsivenessNo issues