Mendokumentasikan sesi coding AI secara otomatis dengan menangkap transkrip dan mengubahnya menjadi standup, laporan, ADR, dan deskripsi PR.
Juga dikenal sebagai MUSE-CODE-SPACE/vibe-coding-mcp, vibe-coding-mcp
- Stars
- 1
- Tools
- 17
- Unduhan, 30 hari
- —
- Versi terbaru
- 2.12.1
- Commit terakhir
- 22 Okt 2026
- Lisensi
- MIT
Apa itu vibe-coding MCP?
Mendokumentasikan sesi coding AI secara otomatis dengan menangkap transkrip dan mengubahnya menjadi standup, laporan, ADR, dan deskripsi PR. Server ini menyediakan 17 tool, seperti muse_capture_transcript, muse_digest, muse_session_history.
Ringkasan dibuat dari README proyek
Tentang vibe-coding MCP server
vibe-coding-mcp adalah tool dokumentasi yang dirancang untuk developer yang menggunakan Claude Code untuk merekam dan mentransformasi sesi coding AI secara otomatis. Tool ini bekerja dengan memparsing transkrip sesi yang tersimpan di direktori lokal Anda untuk menangkap prompt, perubahan file, command yang dieksekusi, dan keputusan desain. Proses ini terjadi secara lokal di disk Anda tanpa memerlukan API key untuk capture awal, memastikan data Anda tetap privat sampai Anda memilih untuk mempublikasikannya.
Server ini menyediakan 17 tool khusus, seperti muse_digest untuk membuat laporan dan muse_publish_document untuk mengekspor konten. Pengguna dapat mengintegrasikan workflow mereka dengan platform seperti Notion, Obsidian, GitHub Wiki, Confluence, Slack, atau Discord. Dengan menginstal hooks ke dalam settings Claude Code Anda, server ini mengubah riwayat percakapan mentah menjadi aset terstruktur seperti standup, laporan mingguan, ADR, dan deskripsi PR melalui slash commands sederhana atau permintaan bahasa alami.
Apa yang bisa Anda lakukan dengannya
- 1Membuat deskripsi pull requestAnda dapat mengotomatiskan pembuatan deskripsi PR dengan menganalisis keputusan desain dan perubahan kode dari sesi tertentu.
- 2Mendokumentasikan keputusan arsitekturTool ini dapat mengekstrak alasan di balik pilihan teknis dan mempublikasikannya langsung ke Obsidian vault sebagai ADR.
- 3Mencari konteks coding historisDeveloper dapat melakukan query pada sesi terdahulu menggunakan keyword atau file path tertentu untuk memahami mengapa jalur implementasi tertentu diambil.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal vibe-coding MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal vibe-coding MCP di Claude Code
$ claude mcp add vibe-coding-mcp -- npx -y vibe-coding-mcpInstal vibe-coding MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"vibe-coding-mcp": {
"command": "npx",
"args": [
"-y",
"vibe-coding-mcp"
]
}
}
}Instal vibe-coding MCP di VS Code
.vscode/mcp.json
{
"servers": {
"vibe-coding-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vibe-coding-mcp"
]
}
}
}Instal vibe-coding MCP di VS Code CLI
$ code --add-mcp '{"name":"vibe-coding-mcp","type":"stdio","command":"npx","args":["-y","vibe-coding-mcp"]}'Instal vibe-coding MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"vibe-coding-mcp": {
"command": "npx",
"args": [
"-y",
"vibe-coding-mcp"
]
}
}
}Instal vibe-coding MCP di Codex
$ codex mcp add vibe-coding-mcp -- npx -y vibe-coding-mcpInstal vibe-coding MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.vibe-coding-mcp] command = "npx" args = ["-y", "vibe-coding-mcp"]
Instal vibe-coding MCP di Gemini CLI
$ gemini mcp add -s user vibe-coding-mcp npx -- -y vibe-coding-mcpInstal vibe-coding MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"vibe-coding-mcp": {
"command": "npx",
"args": [
"-y",
"vibe-coding-mcp"
]
}
}
}Tool vibe-coding MCP 17
Terdeteksi dari READMEmuse_capture_transcriptmuse_digestmuse_session_historymuse_session_statsmuse_summarize_design_decisionsmuse_analyze_codemuse_generate_dev_documentmuse_create_session_logmuse_export_sessionmuse_normalize_for_platformmuse_publish_documentmuse_collect_code_context
| muse_capture_transcript | — | |
| muse_digest | — | |
| muse_session_history | — | |
| muse_session_stats | — | |
| muse_summarize_design_decisions | — | |
| muse_analyze_code | — | |
| muse_generate_dev_document | — | |
| muse_create_session_log | — | |
| muse_export_session | — | |
| muse_normalize_for_platform | — | |
| muse_publish_document | — | |
| muse_collect_code_context | — |
Tampilkan semua 17 toolTampilkan lebih sedikit tool
muse_gitmuse_auto_tagmuse_templatemuse_project_profilemuse_batch
| muse_git | — | |
| muse_auto_tag | — | |
| muse_template | — | |
| muse_project_profile | — | |
| muse_batch | — |
Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaumuse-code-space/vibe-coding-mcp is public and reachablegithub.com/muse-code-space/vibe-coding-mcp ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyavibe-coding-mcp names muse-code-space/vibe-coding-mcp as sourcenpmjs.com/package/vibe-coding-mcp ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-22github.com/muse-code-space/vibe-coding-mcp ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from vibe-coding-mcpLolos
- Tidak ada advisory kritis pada paket atau dependensinya149 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubvibe-coding-mcp
Your AI coding sessions, documented automatically. Captures every Claude Code session from its transcript — prompts, files changed, commands, design decisions — then turns them into standups, weekly reports, ADRs and PR descriptions, and publishes them to Notion / Obsidian / GitHub Wiki / Confluence / Slack / Discord.
Why vibe-coding?
You spent four hours pair-programming with Claude. You made three architectural decisions, wrote eight files, and reverted twice. Tomorrow you will not remember why you picked the second option over the first. Most people solve this with manual journaling that lasts two weeks, or by trawling git log after the fact — and git log knows what changed, not why.
vibe-coding-mcp fixes that at the source. Claude Code already writes a full transcript of every session to ~/.claude/projects/. A tiny hook (vibe-coding-mcp hook) parses that transcript after every turn and stores a structured session locally: what you asked, which files were written or edited (with the code), which commands ran, how long it took, which branch, and the design decisions it can detect in the conversation. From there, 17 MCP tools turn those sessions into a standup, a weekly report, a daily log, a DESIGN / ADR / README / API doc, or a PR description, and publish them anywhere.
No API key needed for capture. Everything stays on your disk until you publish.
30-second install
# 1. Register the MCP server with Claude Code (tools, resources, slash-command prompts)
claude mcp add -s user vibe-coding-mcp -- npx -y vibe-coding-mcp
# 2. Install the capture hooks into ~/.claude/settings.json (backup written first)
npx -y vibe-coding-mcp init
# 3. Restart Claude Code. Then import the sessions you already have and check health
npx -y vibe-coding-mcp capture --all
npx -y vibe-coding-mcp doctor
Then, inside Claude Code:
/standup → Yesterday / Today / Blockers from captured sessions
/weekly-report → Shipped / Decisions / In progress / Next, per project
/daily-vibe-log → today's sessions as one log, offer to publish
@vibe-coding://search/redis → every session that touched redis (titles, prompts, or file paths)
Or just ask: "why did we choose JWT over sessions last week?", "document yesterday's session as a DESIGN doc and put it in my Obsidian vault", "write the PR description for this refactor".
Upgrading from v2.14? The old README's hook recipe used
claude mcp call, which is not a real Claude Code command, so nothing was ever captured. Runnpx vibe-coding-mcp initand remove the old entries. Seedocs/AUTO_CAPTURE.md.
What's new in v2.15.0
- Auto-capture that works.
vibe-coding-mcp hookreads Claude Code's hook JSON on stdin, parses the session transcript, and upserts one session per Claude session (idempotent, exit 0 always, nothing on stdout). init/doctor/captureCLI. Install the hooks with a merge + backup, diagnose, backfill history.muse_digest. Standup / weekly / monthly report over captured sessions, grouped by day · project · tag, English or Korean.muse_capture_transcript. Capture on demand from inside the chat ("save this session").- Resources
vibe-coding://sessions/today,vibe-coding://search/{query}and prompts/standup,/weekly-report. - Agent Skill.
skills/vibe-coding/tells any skill-aware agent (Claude Code, Cursor, Codex, …) when and how to use the server.npm run skill:packbuilds the zip.
Real use cases
1. "Write my standup"
/standup calls muse_digest for yesterday and today plus muse_git status, and returns three bullet groups. Every bullet traces to a captured session title, file path, or decision — nothing invented.
2. "What did I ship this week?" (for your 1:1, Slack, or Notion)
/weekly-report calls muse_digest { period: "week", groupBy: "project" }: totals (sessions, hours, files, decisions), highlights (decisions with rationale), per-project sessions with the files they touched, and most-touched files. Optionally muse_publish_document to Notion / Slack.
3. "Why did we pick option B?"
@vibe-coding://search/<keyword> matches titles, summaries, tags and touched file paths. Open the session; designDecisions holds problem → choice → rationale, and summary holds the actual prompts you typed. This is the context a diff cannot give you.
4. "PR description for a refactor that touched 11 files"
/refactor-context chains session → muse_summarize_design_decisions → muse_analyze_code (AST + Mermaid) → muse_git diff into Why / What changed / Trade-offs / How to review.
5. "Fill my Obsidian vault with ADRs"
muse_summarize_design_decisions over a session, muse_generate_dev_document { documentType: "DESIGN" }, muse_publish_document { platform: "obsidian" } — frontmatter, tags and a session back-reference included.
Tools / Resources / Prompts
| Name | Type | What it does |
|---|---|---|
muse_capture_transcript |
tool | (new) Claude Code transcript → stored session (capture / preview / list, all for backfill) |
muse_digest |
tool | (new) Standup / weekly / monthly report over captured sessions, grouped by day / project / tag |
muse_session_history |
tool | save / get / update / delete / list / search / stats over ~/.vibe-coding-mcp/sessions/ |
muse_session_stats |
tool | Productivity dashboard: sessions/day, decisions/session, language breakdown |
muse_summarize_design_decisions |
tool | Extract decisions (problem → options → choice → trade-off), EN/KO, optional Claude API |
muse_analyze_code |
tool | AST analysis (TypeScript / Python / Go) + Mermaid diagrams |
muse_generate_dev_document |
tool | README / DESIGN / TUTORIAL / CHANGELOG / API / ARCHITECTURE generator |
muse_create_session_log |
tool | Daily or per-session log composition |
muse_export_session |
tool | Export sessions to Markdown / JSON / HTML |
muse_normalize_for_platform |
tool | Markdown quirks for Notion / GitHub Wiki / Obsidian |
muse_publish_document |
tool | Publish to Notion / GitHub Wiki / Obsidian / Confluence / Slack / Discord |
muse_collect_code_context |
tool | Pull code blocks + summary out of raw text |
muse_git |
tool | status / log / diff / branch / snapshot + decision extraction from commits |
muse_auto_tag |
tool | Tag suggestions (Claude API, optional) |
muse_template |
tool | Custom doc templates |
muse_project_profile |
tool | Per-project defaults (platform, tags, language) |
muse_batch |
tool | Several tool calls in one round-trip |
vibe-coding://sessions/list |
resource | All captured sessions |
vibe-coding://sessions/today |
resource | (new) Sessions started today, with files touched |
vibe-coding://sessions/{id} |
resource | One session in full |
vibe-coding://search/{query} |
resource | (new) Keyword search incl. file paths |
vibe-coding://config |
resource | Which publish platforms are configured |
/daily-vibe-log |
prompt | Today's sessions → one daily log |
/standup |
prompt | (new) Yesterday / Today / Blockers |
/weekly-report |
prompt | (new) Shipped / Decisions / In progress / Next |
/document-session |
prompt | Session → dev document → publish |
/refactor-context |
prompt | Session → PR description |
The skill
skills/vibe-coding/ is an Agent Skill (SKILL.md + references/ + scripts/setup.sh + assets/). It teaches the agent: check that capture is running before reporting, which tool chain matches which request, output shapes for standup / weekly / PR, and the rule that every reported line must trace to a captured session. Install it alongside the MCP server:
# Claude Code: drop it into your skills directory
cp -r skills/vibe-coding ~/.claude/skills/
# or build a zip for a marketplace (Agensi, etc.)
npm run skill:pack # → dist-skill/vibe-coding-skill-<version>.zip
How it works
Claude Code ──Stop / SessionEnd hook──▶ vibe-coding-mcp hook ──▶ ~/.vibe-coding-mcp/sessions/*.json
│ (stdin: session_id, │ parse ~/.claude/projects/<slug>/<id>.jsonl
│ transcript_path, cwd) │ prompts · files+code · commands · timing · decisions
│ │ upsert by claudeSessionId
▼
Claude (or any MCP client) ──▶ src/cli.ts ──▶ src/stdio.ts ─┐
src/index.ts (HTTP, POST /mcp) ─┴─▶ src/core/mcpServerFactory.ts
├─ toolRegistry.ts (17 muse_* tools)
├─ resources.ts (5 resources)
└─ prompts.ts (5 prompts)
│
▼
src/tools/*.ts · src/core/{captureEngine,transcriptParser}.ts
src/core/sessionStorage.ts · src/platforms/*.ts
Design choices that matter:
- Capture reads the transcript, not the editor. Claude Code already logs everything; we parse it after the fact. The hook does no network calls, writes nothing to stdout, and exits 0 even on failure, so it can never slow down or break a session.
- One session per Claude session. The
Stophook fires after every turn; captures are keyed onclaudeSessionIdand update in place. User-added tags survive updates. - Local-first.
~/.vibe-coding-mcp/sessions/<id>.json. No DB, no telemetry.grep, back up, or sync it however you like. - One registry, two transports. HTTP and stdio expose the same 17 tools / 5 resources / 5 prompts via
createMcpServer().
CLI reference
vibe-coding-mcp start the MCP server (stdio)
vibe-coding-mcp init install Stop + SessionEnd hooks into ~/.claude/settings.json
--project | --local target .claude/settings.json | .claude/settings.local.json
--dry-run | --print show merged file | print only the hooks block
--remove uninstall
--command "<cmd>" custom hook command
vibe-coding-mcp capture capture the newest transcript for the cwd
--all every transcript for the cwd (backfill)
--transcript <path> --cwd <dir> --dry-run --json
vibe-coding-mcp doctor hooks · transcripts · store · last hook run · platforms
vibe-coding-mcp hook (used by the hooks) stdin JSON → capture
Configuration
| Env var | Required for | Purpose |
|---|---|---|
| (none) | capture, digest, search, docs | Works with zero configuration |
ANTHROPIC_API_KEY |
useAI options, muse_auto_tag |
Claude-API-powered analysis |
NOTION_API_KEY + NOTION_DATABASE_ID |
Notion publishing | |
GITHUB_TOKEN + GITHUB_REPO |
GitHub Wiki publishing | |
OBSIDIAN_VAULT_PATH |
Obsidian default vault | or pass options.vaultPath |
CONFLUENCE_BASE_URL + CONFLUENCE_USERNAME + CONFLUENCE_API_TOKEN + CONFLUENCE_SPACE_KEY |
Confluence | |
SLACK_WEBHOOK_URL / DISCORD_WEBHOOK_URL |
Slack / Discord | |
VIBE_CODING_STORAGE_DIR |
— | Move the session store |
CLAUDE_CONFIG_DIR |
— | If Claude Code's config is not in ~/.claude |
PORT |
HTTP mode only | default 3000 |
Tools that need an unconfigured integration return a structured INTEGRATION_NOT_CONFIGURED error instead of crashing.
Known limitations
- Claude Code only (for now). Capture parses Claude Code's transcript format. Cursor / Codex transcripts are on the roadmap. The MCP tools themselves work from any MCP client.
- Decision extraction is heuristic unless
useAI: truewith an API key: it looks for "decided / chose / instead of / because" patterns in EN and KO. - AST analysis covers TS / Python / Go.
- Publishing is one-way. Edits made in Notion / Wiki are not pulled back.
- Single-user store. Team search across everyone's sessions needs a shared store (roadmap).
When NOT to use this
- Automatic commit messages → use aicommits or similar; this generates documents.
- Team-wide search across everyone's sessions → build a Notion DB on top, or wait for the shared store.
- Hand-written rich notes → use Obsidian / Notion directly; this is capture-then-publish.
Roadmap
- Cursor / Codex CLI transcript capture.
- Shared session store (S3 / Git / WebDAV) and team mode.
prepare-commit-msgsuggestions from the current session's decisions.- Rust / Swift / Kotlin AST + diagrams.
Contributing
git clone https://github.com/MUSE-CODE-SPACE/vibe-coding-mcp
cd vibe-coding-mcp
npm install
npm run typecheck && npm test && npm run build
node dist/cli.js capture --dry-run # try the capture engine on your own transcript
Adding a tool is one file in src/tools/<name>.ts, a Zod schema in src/core/schemas.ts, and one entry in src/core/toolRegistry.ts. CI runs typecheck + build + tests on Node 22 and 24.
Security
Paths are validated, filenames sanitized, webhook URLs must be HTTPS and allowlisted, outbound HTTP has timeouts and backoff — see src/core/security.ts and SECURITY.md. The capture hook stores only your prompts, the assistant's prose, the code it wrote, and the commands it ran; tool outputs, sub-agent side-chains and system reminders are dropped.
Report vulnerabilities privately via a GitHub Security Advisory: https://github.com/MUSE-CODE-SPACE/vibe-coding-mcp/security/advisories/new.
License
MIT — see LICENSE.
Maintainer
@yoon-k (MUSE-CODE-SPACE). Issues + support: https://github.com/MUSE-CODE-SPACE/vibe-coding-mcp/issues.
한국어 요약
vibe-coding-mcp는 Claude Code 세션을 자동으로 문서화하는 MCP 서버 + 에이전트 스킬입니다. Claude Code가 남기는 트랜스크립트(~/.claude/projects/)를 훅이 매 턴마다 파싱해서 프롬프트 · 수정한 파일과 코드 · 실행한 명령 · 소요 시간 · 브랜치 · 설계 결정을 ~/.vibe-coding-mcp/sessions/에 저장합니다. API 키 없이 동작하고, 발행하기 전까지는 아무것도 외부로 나가지 않습니다.
claude mcp add -s user vibe-coding-mcp -- npx -y vibe-coding-mcp # MCP 등록
npx -y vibe-coding-mcp init # 훅 설치 (settings.json 백업 후 병합)
npx -y vibe-coding-mcp capture --all # 기존 세션 가져오기
npx -y vibe-coding-mcp doctor # 상태 확인
Claude Code 안에서 /standup(어제·오늘·블로커), /weekly-report(주간 보고, language: ko 지원), /daily-vibe-log, @vibe-coding://search/키워드를 바로 쓸 수 있고, "지난주에 왜 JWT를 골랐지?", "어제 세션을 DESIGN 문서로 만들어서 Obsidian에 넣어줘", "이 리팩터링 PR 설명 써줘" 같은 요청에 muse_* 도구 17개가 대응합니다.
v2.14의 훅 레시피(
claude mcp call)는 존재하지 않는 명령이라 실제로 캡처가 되지 않았습니다. v2.15에서init으로 교체하세요.
설치·검증·백필은 docs/AUTO_CAPTURE.md, 변경 이력은 CHANGELOG.md, 스킬 패키지는 skills/vibe-coding/ 참고.
Pertanyaan tentang vibe-coding MCP
Bagaimana cara menambahkan vibe-coding MCP ke Claude Code?
Jalankan claude mcp add vibe-coding-mcp -- npx -y vibe-coding-mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan vibe-coding MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan vibe-coding MCP?
Server ini menyediakan 17 tool, termasuk muse_capture_transcript, muse_digest, muse_session_history, muse_session_stats, muse_summarize_design_decisions.
Apakah memerlukan API key untuk menangkap sesi?
Tidak, tidak diperlukan API key untuk proses capture. Semuanya disimpan secara lokal di disk Anda sampai Anda memilih untuk mempublikasikannya.
Bisakah saya menggunakannya untuk membuat deskripsi PR?
Ya, Anda dapat menggunakan prompt /refactor-context untuk menggabungkan data sesi, ringkasan keputusan desain, dan git diffs menjadi sebuah deskripsi PR.
Platform apa saja yang bisa digunakan untuk mempublikasikan dokumentasi saya?
Anda dapat mempublikasikan dokumen ke Notion, Obsidian, GitHub Wiki, Confluence, Slack, dan Discord.