# loopback [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/joshidikshant/loopback  
**GitHub Stars:** 0  
**npm Downloads (last month):** 227  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/loopback

## Description
Feedback bus for coding agents: pin feedback on any web app, an agent fixes it, the pin turns green

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "loopback": {
    "command": "npx",
    "args": ["-y","loopback-mcp-server"]
  }
}
```

## Documentation

## What loopback MCP server does

The loopback MCP server turns feedback on a running web application into items that coding agents can process. A widget adds a toolbar and element-anchored pins to an app, allowing someone to describe a problem directly on the affected page. Each item is associated with a project slug and stored in a shared SQLite database at `~/.loopback/loopback.db`.

A pin can include more than its written description. The widget records relevant console output, the route journey leading to the issue, failed network requests and their response bodies, typed reproduction steps, and available LLM run metadata such as a run ID, model, or trace URL. Publicly deployed sites can submit items through `/ingest` instead of using the widget.

## How it works

Run the server separately for each agent over stdio, or keep one HTTP instance running on `127.0.0.1:7077`. The HTTP mode is required by the browser widget and exposes the MCP endpoint at `http://127.0.0.1:7077/mcp`. Multiple agents and projects can use the same local database, with project slugs separating their queues.

The agent workflow is organized around a feedback lifecycle: list items, claim one, investigate and fix it, link the resulting change, mark it fixed, verify the result, and resolve the item. The web queue at `/queue` provides a human-readable view, while item pages support comments and manual status changes. Once an item is verified, the corresponding page can update its pin to green and show the linked change.

## Setup and configuration

Node.js 22.13 or newer is required because the project uses the built-in `node:sqlite`. Installation can use the published package through `npx`, or the repository can be cloned and built with `npm install`.

Register `npx -y loopback-mcp-server` as an MCP server in the agent configuration. Claude Code, Codex, and Gemini CLI each have documented registration paths. For a shared HTTP process, start `loopback-mcp-server --http` and keep it running with a process manager or operating-system service.

Add the widget script to an application with `data-project` set to the project slug and `data-endpoint` set to the local server URL. From the application repository, `npx loopback-mcp-server init --project <slug> --write` installs the project instructions and agent-specific configuration. The initialization is designed to be repeatable and non-destructive.

## Tools and capabilities

The loopback MCP server supports agent access to:

- Project-filtered feedback queues
- Item details, comments, and status changes
- Claiming work for an agent
- Recording linked commits or pull requests
- Marking fixes, verifying them, and resolving items
- Feedback captured from widget pins or `POST /ingest`
- Shared queue access across supported agents

The HTTP service also provides browser-facing queue pages, widget assets, and live status write-back used to update pins after verification.

## Limitations and notes

This is primarily a local workflow: the documented HTTP service listens on `127.0.0.1:7077`, and the default database is stored under the local user’s home directory. The widget requires the long-running HTTP mode; per-invocation stdio is intended for agents that spawn the server directly.

Other MCP clients may require their own configuration and are not described in the provided setup material. Public-site capture uses the `/ingest` route rather than assuming the local widget can reach the server. The server requires Node.js 22.13 or newer and is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/loopback/readme_