LearnLoop MCP server
2026년 10월 17일 커밋실시간으로 팀 프롬프트를 평가하고 코칭하여, Claude Code, VS Code, Copilot 전반의 AI 도입을 개선하기 위한 공유 프롬프트 라이브러리와 위키를 구축합니다.
다른 이름 Bogzx/LearnLoop
- 스타
- 4
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 10월 17일
- 라이선스
- MIT
LearnLoop MCP란?
실시간으로 팀 프롬프트를 평가하고 코칭하여, Claude Code, VS Code, Copilot 전반의 AI 도입을 개선하기 위한 공유 프롬프트 라이브러리와 위키를 구축합니다.
프로젝트 README에서 생성된 요약
LearnLoop MCP server 정보
LearnLoop는 Claude Code, VS Code 또는 Copilot Chat을 사용하는 개발자가 실시간으로 프롬프트 엔지니어링을 코칭받음으로써 팀의 AI 도입을 개선할 수 있도록 지원합니다. 이 시스템은 목표 명확성, 구체성, 컨텍스트 로딩, 제약 조건 명시, 출력 사양 등 5가지 특정 차원을 기준으로 모든 프롬프트를 평가합니다. 코치 도구를 사용하면 서버가 즉각적인 피드백과 교육 루프를 제공하여 사용자가 프롬프트를 LLM에 보내기 전에 취약한 부분을 개선할 수 있도록 돕습니다.
이 솔루션은 팀이 Docker와 Postgres 데이터베이스를 사용하여 배포하는 셀프 호스팅 방식입니다. 규칙 기반 스코어를 사용하는 오프라인 모드로 실행할 수 있지만, 모든 기능을 사용하려면 Gemini API 키가 필요합니다. 서버는 공유 프롬프트 라이브러리와 팀 위키를 관리하며, 성공적인 프롬프트 관행과 검증된 프롬프트를 자동으로 캡처합니다. 이를 통해 팀의 확립된 표준과 문서화된 워크플로우를 바탕으로 향후 프롬프트의 컨텍스트가 풍부해지는 복리 지식 베이스를 구축합니다.
활용 사례
- 1실시간 프롬프트 코칭AI 클라이언트가 코치 도구를 사용하여 교육 및 수정 루프를 실행함으로써 취약한 프롬프트를 개선할 수 있습니다.
- 2자동 지식 캡처시스템이 팀의 관행을 위키에 자동으로 기록하여 공유 지식 베이스를 구축할 수 있습니다.
- 3프롬프트 라이브러리 구축엄격한 점수 기준을 충족하는 고품질 프롬프트가 팀 공유 라이브러리로 자동 승격됩니다.
- 4컨텍스트 인식 프롬프팅개발자는 팀 특화 관행과 검증된 프롬프트를 검색하여 새로운 작업에 더 나은 컨텍스트를 제공할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
구성
TRAILHEAD_API_URLTRAILHEAD_IT_DATABASE_URLTRAILHEAD_LLM
| 이름 | 설명 | 유형 |
|---|---|---|
| TRAILHEAD_API_URL | — | |
| TRAILHEAD_IT_DATABASE_URL | — | |
| TRAILHEAD_LLM | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능bogzx/learnloop is public and reachablegithub.com/bogzx/learnloop ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-17github.com/bogzx/learnloop ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기LearnLoop
A prompting coach for teams. Every prompt sent through Claude.ai, Claude Code, VS Code or Copilot Chat is scored on five dimensions before it goes out. Weak prompts get a short teaching loop; strong ones join the team's prompt library, and the conventions people state are collected into a team wiki that is fed back into the next person's context. A team's way of prompting compounds without anyone writing docs.
- Try the scorer in your browser: https://learnloop-gules.vercel.app/#try
- Video walkthrough: https://www.youtube.com/watch?v=kD6nnJAmRK8
- Run the whole stack, no API key needed: Try it below
Built at PoliHack v19 (April 2026, BMW track "Applications that encourage AI adoption") by @Bogzx, @KunMihai1, @bbeatricecretu and @CosovanuGabi912. Open source (MIT) and self-hosted: there is no hosted service to sign up for.
Trailhead is the codename used inside the code (package names, settings, env vars); LearnLoop is the product name.
How it works
flowchart LR
subgraph clients["Where people prompt"]
BX["Chrome extension<br/>on claude.ai"]
VS["VS Code extension<br/>sidebar"]
MCP["MCP server<br/>Claude Code · Copilot Chat"]
end
DASH["Dashboard<br/>Next.js"]
subgraph api["apps/api · Hono"]
ROUTES["/score · /coach · /improve · /diff<br/>/wiki/* · /prompts/* · /onboard/*"]
LLM["llm.ts"]
end
PG[("Postgres<br/>wiki · library · score history")]
GEM["Gemini<br/>gemini-3-flash-preview"]
RULES["rule-based scorer<br/>TRAILHEAD_LLM=offline"]
LF["Langfuse<br/>optional"]
BX -- "X-Team-Token" --> ROUTES
VS -- "X-Team-Token" --> ROUTES
MCP -- "X-Team-Token" --> ROUTES
DASH -- "read-only proxy" --> ROUTES
ROUTES --> PG
ROUTES --> LLM
LLM --> GEM
LLM -.-> RULES
GEM -. traces .-> LF
The loop, end to end:
- Score. A prompt is sent (Chrome extension) or a code task starts
(Claude Code / Copilot Chat via the MCP
coachtool). The API scores it on the five dimensions below and records the scores for the team's skill arc. - Coach. At 7/10 or more it goes through untouched. Below 7, the
extension holds the send and offers Improve / Send as-is / Edit;
nothing is sent automatically. In Claude Code the
coachtool runs a short teach → revise loop (at most 5 rounds) on the weakest dimension, using a teammate's proven prompt as the example when there is one. - Promote. A prompt that clears a strict bar (unrounded mean ≥ 7, no dimension below 5, and an independent re-score that agrees) joins the team's prompt library, optionally after a teammate's review.
- Remember. When someone states a team convention,
wiki_saverecords it; repeated mentions are deduplicated and become durable after three. - Reuse. The next prompt about the same part of the codebase is scored and coached with that wiki node's conventions and library prompts in context, so the rubric reads against how this team works.
The rubric, and how the score is measured
Every prompt is scored 0–10 on:
goal_clarity— the desired outcome is stated unambiguouslyspecificity— the change itself is named (files, functions, errors)context_loading— the relevant code, docs or examples are referencedconstraint_articulation— what must not change; limits and invariantsoutput_specification— the shape the answer should take
overall is the rounded mean. The rubric text lives in
packages/scoring/src/score-prompt.mjs, and the score comes from one Gemini
call, so it varies from run to run. apps/api/eval/ measures how much on a
golden set of 30 prompts plus a held-out set of 16, reporting run-to-run
spread, how often the coaching and library gates flip, band hits, and whether
better prompts are ranked above worse ones.
What has been measured so far is the rule-based scorer
(packages/scoring/src/heuristic-score.mjs), a transparent baseline that a
model scorer should beat; the two have not been compared yet. CI checks it on
every change:
| Prompt set | Overall in expected band | Pairs ranked the right way round |
|---|---|---|
| golden (30, visible while its rules were written) | 29/30 | 152/152 |
| held-out (16; per its author, written before the rules were frozen and not tuned on, but added in the same commit, so this can't be checked from history) | 14/16 | 38/38 |
The bands were written in this repo, not by independent reviewers, and the
Gemini scorer has not been run on either set yet (it needs a key; one command
in apps/api/eval/README.md). Known misses and
the full method are documented there.
Try it
In your browser, 10 seconds: the Try it section of the landing page runs the rule-based scorer on whatever you type. Nothing leaves the page.
The whole stack, no key, about 2 minutes (Docker with Compose v2):
git clone https://github.com/Bogzx/LearnLoop && cd LearnLoop
TRAILHEAD_LLM=offline docker compose --profile demo up --build
# API on http://localhost:3000, Postgres schema applied, demo team seeded
curl -s -X POST localhost:3000/score -H 'content-type: application/json' \
-H 'X-Team-Token: trailhead_demo_acme_2026' \
-d '{"prompt":"fix the retry","user_id":"me"}'
Offline mode has no model: scoring uses the rule-based scorer, coaching uses
the static templates, and every response says so. --profile demo loads a
fictional team ("Acme Fintech") with a small wiki, four library prompts and
six days of synthetic activity, so the dashboard has something to show.
With Gemini: cp .env.example .env, put a key from
https://aistudio.google.com/apikey in it, and docker compose up.
Then point the clients at it, all described in SELFHOSTING.md:
# Dashboard on http://localhost:3001 (server-side env; the secret never reaches the browser)
TRAILHEAD_API_URL=http://localhost:3000 TRAILHEAD_TEAM_TOKEN=trailhead_demo_acme_2026 \
npm --workspace=apps/dashboard run dev
# Claude Code / Copilot Chat in one of your repos (the MCP package is not on npm,
# so the CLI runs from this clone; `init` registers the repo's team)
cd /path/to/your/repo
node /path/to/LearnLoop/apps/mcp-server/bin/cli.mjs init
Packages of the Chrome extension (.zip, load unpacked) and the VS Code
extension (.vsix) are built by every CI run (the extensions artifact) and
attached to GitHub releases
from v0.1.0; neither is on a store.
Before exposing the API beyond localhost, read
SELFHOSTING.md → Security model.
What's in the box
| Surface | What it does | Code |
|---|---|---|
| API | Hono + TypeScript on Node 22, raw pg. Multi-tenant: each team has a public id and a server-minted secret (stored hashed). Scoring, coaching, library, wiki, rich bootstrap, rate limits, Langfuse tracing. |
apps/api — routes in its README |
| Chrome extension | MV3, on claude.ai. Score card under the composer, score badges on each message, Compare to team diff, Improve chat, outcome chips, wiki toasts, context picker. Every API call goes through the service worker. | apps/browser-ext |
| VS Code extension | Sidebar with the same score card, team examples for the open file, wiki-update toasts. | apps/vscode-ext |
| MCP server | STDIO server for Claude Code and Copilot Chat: coach, wiki_lookup, wiki_save, wiki_bootstrap, wiki_proven_prompts (+ ping), and a CLI: init, bootstrap, reset. |
apps/mcp-server |
| Dashboard | Next.js 16: team skill arc, metrics, wiki tree, onboarding view; reads through a server-side proxy so the team secret stays on the server. | apps/dashboard |
| Landing page | Static page with the in-browser scorer. | apps/landing-page |
| Shared packages | shared (every request/response type), scoring (prompts, rubric, rule-based scorer, renderers), score-card (DOM score card), db (schema, migrations, demo seed). |
packages/ |
Postgres holds eight tables (packages/db/schema.sql): teams, wiki nodes,
learnings, library prompts, captures, skill observations, and the two
rich-bootstrap job tables.
Development
Node ≥ 22.6, npm workspaces.
npm ci
npm run typecheck # tsc --noEmit in every workspace
npm run lint # ESLint flat config
npm test # every workspace's tests, including the scorer baseline
npm run build # every workspace with a build script
# API integration tests against a throwaway Postgres (they wipe it):
docker run -d --rm --name trailhead-it -p 55432:5432 -e POSTGRES_USER=trailhead \
-e POSTGRES_PASSWORD=trailhead -e POSTGRES_DB=trailhead_it postgres:16-alpine
TRAILHEAD_IT_DATABASE_URL=postgresql://trailhead:trailhead@127.0.0.1:55432/trailhead_it \
npm --workspace=apps/api run test:integration
CI runs all of that, plus npm audit, a Docker build with a
docker compose up smoke test in offline mode, and packaging of both
extensions. A v* tag attaches the extension packages to a draft release
(.github/workflows/release.yml).
Without Docker, the API runs against any Postgres:
psql "$DATABASE_URL" -f packages/db/schema.sql, optionally
node packages/db/seed.mjs, then npm run dev (reads .env).
Deployment
- API: self-hosted.
docker composeas above, or any Node 22 host (railway.jsonis kept for Railway). Every environment variable is in SELFHOSTING.md → All variables. - Dashboard: Vercel or any Next.js host. Set
TRAILHEAD_API_URLandTRAILHEAD_TEAM_TOKENserver-side; anyone who can open it can read that team's data, so restrict access. - Landing page: static files on Vercel.
- Extensions: from the release packages, loaded unpacked / installed from
the
.vsix.
Specs
The project was specced before it was built; the specs are the record of why:
docs/superpowers/specs/2026-04-25-trailhead-design.md— master specdocs/superpowers/specs/2026-04-25-mcp-plugin-ux-design.md— MCP install story and (then) four-tool surfacedocs/superpowers/specs/2026-04-25-trailhead-browser-ext-design.md— Claude.ai content-script architecturedocs/superpowers/specs/2026-04-25-demo-completion-design.md— dashboard and seeding plandocs/superpowers/specs/2026-04-26-trailhead-educational-loop-design.md— the teach → reveal coaching loopdocs/superpowers/specs/2026-04-26-wiki-bootstrap-rich-design.md— async rich bootstrapdocs/superpowers/specs/2026-04-26-improve-widget-design.md— multi-turn improve widgetdocs/roadmaps/— per-surface 24-hour build plans
Each app and package has its own README with surface-specific details.
License
MIT — see LICENSE.
LearnLoop MCP 질문
Claude Code에서 코칭 루프는 어떻게 작동하나요?
Claude Code에서 코치 도구는 프롬프트의 가장 취약한 차원을 대상으로 최대 5라운드에 걸친 교육 및 수정 루프를 실행합니다.
LearnLoop는 호스팅 서비스인가요?
아니요, LearnLoop는 오픈 소스 셀프 호스팅 제품이며 별도의 호스팅 서비스 가입은 필요하지 않습니다.