Vibe Coding

You run a dedicated MCP server that automatically collects, summarizes, documents, and publishes code and design decisions from vibe coding sessions. It provides a structured workflow to generate documentation, export sessions, and publish results to Notion, GitHub Wiki, Obsidian, Confluence, Slack, or Discord, helping your team capture decisions and code context over time.

How to use

Start the MCP server and connect with an MCP client to guide your workflow. You can collect code blocks and conversation summaries, extract design decisions, generate documents like README and DESIGN, normalize outputs for your publishing platform, and then publish to your chosen destination. Use the batch tools to run multiple steps in sequence or in parallel, and export sessions in Markdown, JSON, or HTML for sharing.

How to install

Prerequisites: you need Node.js and npm, or you can run the MCP server via a CLI tool if your environment provides it.

Install the MCP client/CLI tool that exposes the vibe-coding MCP server interface.

# Claude Code recommended (adds the MCP server to Claude):
claude mcp add vibe-coding-mcp npx vibe-coding-mcp

# npm global install (alternative):
npm install -g vibe-coding-mcp

If you plan to run via Claude Desktop, prepare the configuration for the local client as shown below.

{
  "mcpServers": {
    "vibe_coding_mcp": {
      "command": "npx",
      "args": ["vibe-coding-mcp"]
    }
  }
}

Additional setup notes

The MCP server supports multiple publishing platforms and offers environment variables to configure API keys and platform access. If you need to enable AI-powered analysis, set the useAI option to true in your tool parameters.

Configuration and platform publishing

You can publish generated documents to external platforms such as Notion, GitHub Wiki, Obsidian, Confluence, Slack, and Discord. Ensure you have the appropriate API tokens and IDs for the chosen platforms. The server provides templates, session exports, and document generation options to tailor outputs for each destination.

Examples of common workflows

Generate documentation from a coding session and publish it to a Notion page in one flow: emit inputs that collect code context, summarize design decisions, generate the documentation, normalize for Notion, and publish.

Troubleshooting tips

If a publishing step fails, check network access to the target platform and verify that the required API keys or tokens are correctly configured in your environment variables.

Available tools

muse_collect_code_context

Collects code blocks and conversation summaries into structured context

muse_summarize_design_decisions

Extracts key architectural and design decisions from conversation logs

muse_generate_dev_document

Generates README, DESIGN, TUTORIAL, CHANGELOG, API, or ARCHITECTURE documents

muse_normalize_for_platform

Converts Markdown documents for Notion, GitHub Wiki, or Obsidian

muse_publish_document

Publishes generated documents to external platforms

muse_create_session_log

Creates daily or session-based vibe coding session logs

muse_analyze_code

AST-based code analysis with Mermaid diagram generation

muse_session_history

Manages session history - save, retrieve, search past sessions

muse_export_session

Exports sessions to Markdown, JSON, or HTML formats

muse_project_profile

Manages project-specific settings and configurations

muse_git

Git integration - status, log, diff, branch, snapshot, design decision extraction

muse_session_stats

Session analytics dashboard with productivity insights and trends

muse_auto_tag

AI-powered auto-tagging for sessions based on content analysis

muse_template

Custom template management for documents and reports

muse_batch

Batch operations to execute multiple tools in sequence or parallel