Vibe MCP Server

Auto-document vibe coding sessions - collect, summarize, and publish. The vibe mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

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.

Its toolset

Everything the assistant can do here goes through one of these:

• muse_collect_code_context — tool
• muse_summarize_design_decisions — tool
• muse_analyze_code — tool
• muse_generate_dev_document — tool
• muse_normalize_for_platform — tool
• muse_publish_document — tool
• muse_create_session_log — tool
• muse_session_history — tool
• muse_export_session — tool
• muse_project_profile — tool
• muse_git — tool
• muse_session_stats — tool

Configuration

You will need 8 environment variables: ANTHROPIC_API_KEY, NOTION_API_KEY, NOTION_DATABASE_ID, GITHUB_TOKEN, CONFLUENCE_BASE_URL, CONFLUENCE_API_TOKEN, SLACK_WEBHOOK_URL, DISCORD_WEBHOOK_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at vibe-coding-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Vibe's toolset — muse_collect_code_context, muse_summarize_design_decisions, muse_analyze_code and 11 more — is a fair guide to whether it matches your workflow. It is maintained by MUSE-CODE-SPACE; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vibe.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vibe mcp server does with a few real requests.