Loopback MCP server
2026년 11월 12일 커밋코딩 에이전트가 MCP를 통해 결정, 리뷰, 브리핑을 요청할 수 있는 Human-in-the-loop 방식의 웹 인박스를 제공합니다.
다른 이름 LoopBackTools/loopback
- 스타
- 0
- Tools
- 7
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
Loopback MCP란?
코딩 에이전트가 MCP를 통해 결정, 리뷰, 브리핑을 요청할 수 있는 Human-in-the-loop 방식의 웹 인박스를 제공합니다. 7개 도구를 제공합니다. 예: ask_question, request_review, answer_follow_up.
프로젝트 README에서 생성된 요약
Loopback MCP server 정보
Loopback은 코딩 에이전트를 위한 Human-in-the-loop 방식의 웹 인박스를 제공합니다. AI 에이전트가 터미널에서 멈춰 있거나 사용자의 선호도를 추측하는 대신, 실시간 인터페이스를 통해 결정, 리뷰 또는 브리핑을 요청할 수 있도록 지원합니다. 개발자는 이 도구를 사용하여 여러 프로젝트에 걸친 에이전트 상호작용을 하나의 중앙 집중식 대시보드에서 관리할 수 있습니다.
이 MCP server는 Cloudflare Workers에서 Durable Objects와 SQLite를 사용하여 실행되므로 요청이 유실되지 않습니다. 사용자의 Cloudflare 계정에 직접 배포되며, 인증을 위해 secret token이 필요합니다. 사용자는 백그라운드 작업 지원이 없는 클라이언트를 위해 폴링 방식을 사용하는 Free 플랜과, 더 빠른 폴링 및 차단형 질문에 대한 더 긴 대기 시간을 제공하는 Paid 플랜 중 선택할 수 있습니다.
시스템에는 간단한 질의를 위한 ask_question, 코드나 diff를 검토하기 위한 request_review, 복잡하고 상세한 설명을 위한 send_briefing과 같은 특정 도구가 포함되어 있습니다. 또한 에이전트의 질문을 인박스로 자동 라우팅하는 Claude Code 플러그인 기능도 제공합니다.
활용 사례
- 1에이전트 생성 코드 리뷰에이전트가 변경 사항을 진행하기 전에 승인을 받기 위해 diff 또는 계획을 제시할 수 있습니다.
- 2복잡한 설명 관리여러 항목으로 구성된 브리핑에 대해 한 번에 하나씩 응답하여 복잡한 기술적 설명을 해결할 수 있습니다.
- 3Claude Code 상호작용 자동화수동 설정 없이 Claude Code의 모든 질문을 웹 인박스로 직접 라우팅할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Loopback MCP 도구 7
README에서 감지됨ask_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 | — |
구성
CLOUDFLARE_ACCOUNT_IDLOOPBACK_PLANLOOPBACK_URL
| 이름 | 설명 | 유형 |
|---|---|---|
| CLOUDFLARE_ACCOUNT_ID | — | |
| LOOPBACK_PLAN | — | |
| LOOPBACK_URL | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능loopbacktools/loopback is public and reachablegithub.com/loopbacktools/loopback ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/loopbacktools/loopback ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음7 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기When 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 질문
Loopback MCP는 어떤 도구를 제공하나요?
7개 도구를 제공합니다. 예: ask_question, request_review, answer_follow_up, send_briefing, answer_briefing.
에이전트가 Loopback과 어떻게 상호작용하나요?
에이전트는 ask_question, request_review, send_briefing과 같은 MCP 도구를 사용하여 실시간 웹 인박스와 통신합니다.
Claude Code에서 Loopback을 사용할 수 있나요?
네, Claude Code가 사용자에게 던지는 모든 질문을 Loopback으로 자동 라우팅하는 전용 Claude Code 플러그인이 있습니다.