Feedback bus for coding agents: pin feedback on any web app, an agent fixes it, the pin turns green
Feedback bus for coding agents: pin feedback on any web app, an agent fixes it, the pin turns green
Loopback is the interactive feedback layer between real product usage and your coding agents: one script tag makes the app you're running locally commentable (Vercel-toolbar-style toolbar, element-anchored pins; deployed public sites go via the /ingest rails instead — see surface compatibility), every pin auto-captures the functional context — failing requests with response bodies, console trail, the route journey that led there, LLM run metadata, typed repro steps — and lands in one project-tagged queue that Claude Code, Codex, and Gemini CLI all work over MCP.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| loopback_submit_feedback | File an item: project, type ui\ |
| loopback_list_feedback | Filter (project/route/status/type/severity/source/assignee) + paginate (total/has_more/next_offset); severity-then-newest |
| loopback_get_feedback | Full item: all context + linked change + comment trail |
| loopback_update_feedback | Correct an item after filing: title, body, severity, type, project, or route — re-rank a severity, fix a mis-guessed type, move it to the right project |
| loopback_claim_feedback | **Atomic** claim; a conflict names the holder; force to take over; open/triaged → in_progress |
| loopback_update_status | open → triaged → in_progress → fixed → verified \ |
| loopback_add_comment | Root-cause notes, questions, reasoning trail |
| loopback_link_change | Merge repo/branch/commit/pr_url/diff_summary onto the item |
| loopback_resolve_feedback | Close as verified (confirmed for real) or wontfix |
| loopback_get_stats | project × status counts |
{
"mcpServers": {
"loopback-server": {
"command": "npx",
"args": ["-y", "loopback-mcp-server"],
"env": {
"LOOPBACK_HOST": "your-value",
"LOOPBACK_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| LOOPBACK_HOST | Endpoint or connection string the server talks to. | Optional |
| LOOPBACK_TOKEN | Credential the server authenticates with. | Yes |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
MCP server wrapping the Taskwarrior CLI for structured, project-scoped task management.
Trust-aware repository facts for agents: build, test, docs, license, and security, no scraping.
Local code-memory graph for AI coding agents.
<strong>Perforce P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the Perforce P4 version control system. It is built on