Loopback MCP server
Commit 12. Nov. 2026Bietet ein Human-in-the-loop Web-Inbox für Coding-Agents, um Entscheidungen, Reviews und Briefings via MCP anzufordern.
Auch bekannt als LoopBackTools/loopback
- Stars
- 0
- Tools
- 7
- Downloads, 30 Tage
- —
- Neueste Version
- —
- Letzter Commit
- 12. Nov. 2026
- Lizenz
- MIT
Was ist Loopback MCP?
Bietet ein Human-in-the-loop Web-Inbox für Coding-Agents, um Entscheidungen, Reviews und Briefings via MCP anzufordern. Er stellt 7 Tools bereit, etwa ask_question, request_review, answer_follow_up.
Zusammenfassung generiert aus dem README des Projekts
Über Loopback MCP server
Loopback ermöglicht eine Human-in-the-loop Web-Inbox für Coding-Agents. Es erlaubt KI-Agents, Entscheidungen, Reviews oder Briefings über eine Live-Schnittstelle anzufordern, anstatt im Terminal zu blockieren oder Nutzerpräferenzen zu erraten. Entwickler nutzen dies, um Agent-Interaktionen über mehrere Projekte hinweg von einem zentralen Dashboard aus zu verwalten.
Dieser MCP server läuft auf Cloudflare Workers unter Verwendung von Durable Objects und SQLite, um sicherzustellen, dass keine Requests verloren gehen. Er wird in deinem eigenen Cloudflare-Account bereitgestellt und benötigt ein Secret Token zur Authentifizierung. Nutzer können zwischen einem Free-Plan, der Polling für Clients ohne Background-Task-Support nutzt, oder einem Paid-Plan für schnelleres Polling und längere Wartezeiten bei blockierenden Fragen wählen.
Das System enthält spezifische Tools wie ask_question für einfache Abfragen, request_review zur Inspektion von Code oder Diffs und send_briefing für komplexe, punktweise Erklärungen. Zudem gibt es ein Claude Code Plugin, das Agent-Fragen automatisch an die Inbox weiterleitet.
Was du damit machen kannst
- 1Review von agent-generiertem CodeEin Agent kann einen Diff oder einen Plan zur Genehmigung präsentieren, bevor er mit einer Änderung fortfährt.
- 2Verwaltung komplexer ErklärungenDu kannst auf mehrstufige Briefings Punkt für Punkt antworten, um komplexe technische Erklärungen zu klären.
- 3Automatisierung von Claude Code InteraktionenDu kannst alle Fragen von Claude Code ohne manuelle Konfiguration direkt an deine Web-Inbox routen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
Loopback MCP tools 7
Erkannt aus dem READMEask_questionrequest_reviewanswer_follow_upsend_briefinganswer_briefingcreate_image_uploadopen_inbox
| ask_question | — | |
| request_review | — | |
| answer_follow_up | — | |
| send_briefing | — | |
| answer_briefing | — | |
| create_image_upload | — | |
| open_inbox | — |
Konfiguration
CLOUDFLARE_ACCOUNT_IDLOOPBACK_PLANLOOPBACK_URL
| Name | Beschreibung | Typ |
|---|---|---|
| CLOUDFLARE_ACCOUNT_ID | — | |
| LOOPBACK_PLAN | — | |
| LOOPBACK_URL | — |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarloopbacktools/loopback is public and reachablegithub.com/loopbacktools/loopback ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-12github.com/loopbacktools/loopback ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell7 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNo tool named like delete, drop or execBestanden
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenWhen an agent needs a decision, a preference or your sign-off, it asks through Loopback instead of guessing, or stopping in a terminal you are not watching. The ask appears in a live web inbox. You answer there, and your reply comes back to the agent as the result of its tool call, so it carries straight on.
Loopback is an MCP server on Cloudflare Workers: one Worker, one Durable Object per inbox, and the inbox itself served from the same deployment. You run it on your own Cloudflare account.
Features
- Questions and reviews. Agents ask questions, with or without choices, and show you work for a verdict: copy, a plan, code, a diff, a screenshot.
- Briefings, point by point. When an agent explains something that breaks into several points, you reply on each point on its own, drill into it through sub-points the agent adds, and resolve it. Each point is one line until opened, so what still needs you is plain to see.
- Ways to reply that fit the ask. Answer (pick choices, write your own words, or both), approve with an optional note, request changes, ask a question back, reply on a briefing's points, or dismiss.
- Agents don't stop for you. On clients that support MCP background tasks, an ask returns at once and the reply arrives when you give it. Other clients wait, kept alive by progress updates.
- One inbox for every project. Each ask names the project it comes from, so agents in many repositories share one inbox.
- Nothing lost. Asks and replies live in SQLite. A call retried after a dropped connection rejoins the ask it opened, and a reply waits for the agent that asked.
- A live inbox. Grouped by whose turn it is, updated as agents ask, with keyboard shortcuts and opt-in notifications.
- Claude Code plugin. Routes every question Claude Code has for you to Loopback, without your having to ask it to.
- Spec-first API. The REST API, event socket and MCP tools are defined once in TypeSpec, with a typed SDK for building your own inbox.
Tools
| Tool | What it does |
|---|---|
ask_question |
Asks you something, optionally with choices. |
request_review |
Shows you work for your verdict: approve, request changes, ask back or dismiss. |
answer_follow_up |
Answers a question you asked back, keeping the same ask open. |
send_briefing |
Explains something as points you reply on one at a time, and resolve. |
answer_briefing |
Answers your replies on a briefing, point by point, breaking points into sub-points. |
create_image_upload |
Hands out a one-time URL for an image to show in a review. |
open_inbox |
Gives the address of your inbox, or of one ask in it, so the agent can open it for you. |
The server tells agents when to use each tool, so asking an agent to "show me the copy" or "check with me before you pick" is enough.
Quick start
You need a Cloudflare account with R2 enabled, Node 24.22 or later (or 22.23 or later), and pnpm 11.
Loopback deploys with cf, Cloudflare's CLI, which is in
beta; pnpm install installs it for you.
git clone https://github.com/LoopBackTools/loopback.git
cd loopback
pnpm install
pnpm --filter loopback exec cf auth login
printf 'LOOPBACK_TOKEN=%s\n' "$(openssl rand -hex 32)" > ~/loopback.secrets
pnpm run deploy --secrets-file ~/loopback.secrets
The deploy builds the inbox, creates the Worker with your token as its secret, and provisions its R2 bucket.
Open the workers.dev URL the deploy printed, and sign in with the token from ~/loopback.secrets.
Keep the token somewhere safe, such as a password manager, then delete the file. It must be at least
32 characters, and it only ever travels in the Authorization header, which Cloudflare keeps out of
its logs.
Later deploys keep the token, so pnpm run deploy is enough. To change it, put a new one in a
secrets file and deploy with --secrets-file again.
Free or Paid
Loopback is built to run on Cloudflare's Workers Free plan, which holds each request to 10 ms of
CPU. Most of its requests take 2 to 9 ms. The first request a fresh isolate serves, and a blocking
question, take 20 to 65 ms: a copy held to 10 ms on Workers Paid let every one of them through,
but Free itself hasn't been measured. A deployment says which plan it is on with LOOPBACK_PLAN
when it is deployed:
LOOPBACK_PLAN=paid pnpm run deploy
Set it on every deploy: a deploy without it is for Free, and says so. The two differ only in what a deployment spends on agents waiting for you:
| Free (the default) | Paid | |
|---|---|---|
| A blocking question, from a client without background tasks | waits 10 minutes, then tells the agent to call again with the same arguments, which picks up the same question | waits until you answer |
| How often a background task is polled | every 5 s, then 15 s, then 30 s | every 2 s, then 10 s, then 30 s |
To check that a change fits Free, deploy a copy held to Free's 10 ms of CPU per request, drive it with an agent's traffic, and read back what each request cost:
pnpm --filter loopback run deploy --mode cpu-check --secrets-file ~/loopback.secrets
LOOPBACK_URL=https://loopback-cpu-check.<your-subdomain>.workers.dev LOOPBACK_TOKEN=... \
node apps/loopback/scripts/cpu-check.ts
CLOUDFLARE_ACCOUNT_ID=<your account id> \
pnpm --filter loopback exec node scripts/cpu-report.ts loopback-cpu-check <when the check began>
Delete the copy afterwards with pnpm --filter loopback exec cf workers delete loopback-cpu-check,
then empty and delete its bucket, loopback-cpu-check-files.
Connect an agent
Claude Code
Add Loopback's MCP server, for every project, with your token in LOOPBACK_TOKEN:
claude mcp add --scope user --transport http loopback https://<your-worker>/mcp \
--header "Authorization: Bearer $LOOPBACK_TOKEN"
Then install the plugin, which routes every question the agent has for you to Loopback without your having to ask it to. It holds only hooks, so it needs no URL or token:
claude plugin install loopback --marketplace LoopBackTools/loopback
integrations/claude-code explains what it does. Or let the
agent do it: every deployment serves /llms.txt, which tells an agent how to connect itself to that
deployment, for the way its agents sign in, and how to use Loopback once it has.
Any MCP client
Loopback serves MCP over Streamable HTTP at /mcp, authenticated with your token as a bearer
header. Most clients take a configuration like this:
{
"mcpServers": {
"loopback": {
"type": "http",
"url": "https://<your-worker>/mcp",
"headers": { "Authorization": "Bearer <your-token>" }
}
}
}
Behind a login, through the JWT gate, agents sign in with OAuth instead and need no token in their
configuration: docs/hosting.md explains it.
A client that supports MCP background tasks (io.modelcontextprotocol/tasks), such as Claude Code
2.1.304 and later, gets each ask back at once and carries on. A client without them waits for your
reply, which can take minutes. Loopback sends progress updates to keep the call alive, but a client
that caps tool calls at a fixed timeout needs that limit raised.
How it works
The Worker authenticates each request and hands it to a Space Durable Object, which holds the
asks, their threads and the connected inboxes in SQLite. Agents reach it through MCP; the inbox
through a REST API and an event socket. Images go to R2.
docs/architecture.md explains how it fits together.
Build your own inbox
The whole web app is published as @loopbacktools/app: compose it with your
own sign-in and workspaces, and it brings the inbox, its header, routing and the page on connecting
agents. The inbox alone is published as React components, @loopbacktools/inbox,
to render inside an app of your own: it reads and answers through the client you hand it, and moves
between asks through your routes. It is built only on @loopbacktools/sdk, a client for the REST
calls, the live event socket and the inbox state, with a promise API for any framework and an
Effect service, which packages/sdk explains. The API is also described
by an OpenAPI document, served at /api/v1/openapi.json, for clients in any language.
Hosting for many people
One deployment can serve many tenants. Point its JWT gate at any login that issues JWTs, and each
token's claims name the space it opens and the person; every space is its own Durable Object, and
agents sign in with OAuth. docs/hosting.md explains how.
Development
cp apps/loopback/.dev.vars.example apps/loopback/.dev.vars
pnpm dev # the Worker and the inbox, with hot reload
pnpm test # every package's tests
pnpm lint # oxlint
pnpm typecheck
pnpm format # oxfmt
pnpm generate # regenerate the API from its TypeSpec definition
| Path | What it is |
|---|---|
packages/protocol |
The API contract, in TypeSpec, and what is generated from it: types and the OpenAPI document. |
packages/server |
The server: Durable Object, HTTP API, event socket and MCP tools, written in Effect. |
packages/sdk |
A client for building your own inbox, in any framework. |
packages/inbox |
The web inbox as React components, built on the SDK. |
packages/app |
The web app around the inbox, for a deployment to compose with its own sign-in. |
apps/loopback |
The deployable Worker, and the app it serves, signed in with the deployment's token. |
integrations/claude-code |
The Claude Code plugin. |
Contributing
Issues and pull requests are welcome. CONTRIBUTING.md covers setting up, the
checks a change has to pass, and changing the API.
Security
Please report vulnerabilities privately, as SECURITY.md describes, not in a public
issue.
Licence
Loopback MCP Fragen
Welche Tools bietet Loopback MCP?
Er stellt 7 Tools bereit, darunter ask_question, request_review, answer_follow_up, send_briefing, answer_briefing.
Wie interagieren Agents mit Loopback?
Agents nutzen MCP Tools wie ask_question, request_review und send_briefing, um mit einer Live-Web-Inbox zu kommunizieren.
Kann ich Loopback mit Claude Code nutzen?
Ja, es gibt ein spezielles Claude Code Plugin, das jede Frage, die Claude Code an dich hat, automatisch an Loopback weiterleitet.