MCP.Market

Vibe Coding MCP server

by MUSE-CODE-SPACE·io.github.MUSE-CODE-SPACE/vibe-coding·v2.12.1
No reviews yet

Auto-document vibe coding sessions - collect, summarize, and publish

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars48 downloads/wk

Reviews

Write one

Nobody has reviewed Vibe Coding yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vibe Coding tools (15, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • muse_analyze_code

    Performs deep code analysis using AST parsing. Extracts functions, classes, imports, and generates Mermaid diagrams. Supports AI-powered analysis for quality insights, security issues, and improvement suggestions.

  • muse_auto_tag

    Automatically suggests and applies tags to sessions. Actions: suggest (recommend tags), apply (add tags to session), train (learn from examples), config (configure tagging behavior).

  • muse_batchwrite action

    Executes multiple tool operations in batch. Actions: execute (run batch), preview (plan without executing), status (check job status), cancel (stop running job), history (list past jobs). Supports sequential and parallel execution with dependency management.

  • muse_collect_code_context

    Collects code blocks and conversation summaries into a structured context for documentation. Supports automatic language detection, duplicate removal, and statistics.

  • muse_create_session_logwrite action

    Creates daily or session-based vibe coding session logs.

  • muse_export_session

    Exports vibe coding sessions to various formats (Markdown, JSON, HTML). Use for creating shareable documentation, backups, or reports from session history.

  • muse_generate_dev_document

    Generates README, DESIGN, TUTORIAL, or CHANGELOG documents in Markdown format. Supports multiple languages, badges, API reference, FAQ, and more.

  • muse_git

    Git integration for vibe coding sessions. Get repository status, commit history, diffs, branch info. Capture git snapshots for sessions and extract design decisions from commit messages.

  • muse_normalize_for_platform

    Converts Markdown documents for Notion, GitHub Wiki, or Obsidian platforms. Handles links, images, code blocks, tables, frontmatter, and platform-specific syntax.

  • muse_project_profile

    Manages project profiles for vibe coding sessions. Save project-specific settings for documentation, code analysis, and publishing.

  • muse_publish_documentwrite action

    Publishes generated documents to external platforms (Notion, GitHub Wiki, Obsidian, Confluence, Slack, or Discord).

  • muse_session_history

    Manages vibe coding session history. Save, retrieve, search, and manage past coding sessions with their code contexts and design decisions.

  • muse_session_stats

    Provides analytics and insights about coding sessions. Actions: overview (summary stats), languages (language breakdown), timeline (activity over time), tags (tag analysis), productivity (work patterns), trends (compare periods).

  • muse_summarize_design_decisions

    Extracts and analyzes key architectural and design decisions from conversation logs. Supports both English and Korean, with importance scoring and keyword extraction. Set useAI=true for Claude-powered enhanced analysis.

  • muse_template

    Manages custom document templates with variable substitution. Actions: create, get, update, delete, list, apply (render with data), preview (render preview), import, export.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan79 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 87 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vibe Coding compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
48
more than 40% of 12,191 servers with a package

What its tools let an agent do: 12 read · 3 change

Install Vibe Coding in Claude Code, Cursor or VS Code

Runs npx -y vibe-coding-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vibe-coding -- npx -y vibe-coding-mcp
Add to Cursor

What the publisher says

From the Vibe Coding repository's README, as published. We do not edit it. Read it on GitHub

vibe-coding-mcp

Auto-documents your AI coding sessions — wire it as a Claude Code hook and your daily README / design-decision log / refactor-PR description writes itself.

English · 한국어

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 in commit a1b2c3d over the first one you tried. Most people solve this with manual journaling that lasts two weeks, or by trawling git log after the fact.

vibe-coding-mcp solves it differently: it sits as an MCP server next to your editor, collects code blocks and design decisions out of the conversation, generates README / DESIGN / API / ARCHITECTURE documents from them, and publishes to Notion / GitHub Wiki / Obsidian / Confluence / Slack / Discord — all from inside the chat with Claude. Wire it as a Claude Code PostToolUse + Stop hook (one block of JSON, see Quickstart) and every session auto-captures into ~/.vibe-coding-mcp/sessions/ without you typing anything. The bundled daily-vibe-log prompt then rolls today's captures into one document.

The Phase 3 refactor (v2.14.0, May 2026) collapsed the two-entry-point drift (index.ts had 7 tools, stdio.ts had 15) into a single transport-agnostic registry, so HTTP and stdio now expose the same 15 tools, 3 resources, and 3 prompts.

What's new in v2.14.0

  • One registry, two entry points, zero drift. src/core/toolRegistry.ts is the single source of truth — both index.ts (Streamable HTTP) and stdio.ts (bin) load the same 15 tools, 3 resources, and 3 prompts.
  • Migrated to high-level McpServer API (SDK 1.25+). McpServer.registerTool() / .resource() / .prompt() instead of low-level setRequestHandler(CallToolRequestSchema). Adding a tool is now a one-line register() call.
  • Streamable HTTP (MCP 2025-03-26), not SSE. POST /mcp at :3000. The legacy /sse route returns HTTP 410 with a pointer.
  • 3 new MCP Resources for @-mention. vibe-coding://sessions/list (captured sessions), vibe-coding://sessions/{id} (one session in full), vibe-coding://config (current platform creds).
  • 3 new MCP Prompts. daily-vibe-log (roll today's sessions into one doc), document-session (one session → README/DESIGN/API/etc. → publish), refactor-context (session → PR description with decisions + AST analysis + git diff).
  • +34 tests (149 → 183 passing) covering the registry, resources, prompts, and the McpServer factory.

5-minute Quickstart

# 1. Install via Claude Code
claude mcp add vibe-coding-mcp -- npx -y vibe-coding-mcp
  1. Wire it as a Claude Code hook so every session auto-captures. Add this to ~/.claude/settings.json:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vibe Coding: common questions

Is Vibe Coding MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Vibe Coding safety report
How do I install Vibe Coding?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vibe Coding need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vibe Coding maintained?
The last commit was 121 days ago (2026-07-06). The latest release is v2.12.1.
What can I use instead of Vibe Coding?
Servers from other publishers that do the same job: Deja Vu MCP server.
How does Vibe Coding compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Vibe Coding

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A

More from MUSE-CODE-SPACE →