VIBE CODING TOOLS

15 tools from the Vibe Coding MCP Server, categorised by risk level.

View the Vibe Coding policy →

READ TOOLS

2

WRITE TOOLS

11
muse_auto_tag Automatically suggests and applies tags to sessions. Actions: suggest (recommend tags), apply (add tags to session), train (learn from examples), c... 3/5 muse_collect_code_context Collects code blocks and conversation summaries into a structured context for documentation. Supports automatic language detection, duplicate remov... 3/5 muse_create_session_log Creates daily or session-based vibe coding session logs. 2/5 muse_export_session Exports vibe coding sessions to various formats (Markdown, JSON, HTML). Use for creating shareable documentation, backups, or reports from session ... 2/5 muse_generate_dev_document Generates README, DESIGN, TUTORIAL, or CHANGELOG documents in Markdown format. Supports multiple languages, badges, API reference, FAQ, and more. 2/5 muse_normalize_for_platform Converts Markdown documents for Notion, GitHub Wiki, or Obsidian platforms. Handles links, images, code blocks, tables, frontmatter, and platform-s... 2/5 muse_project_profile Manages project profiles for vibe coding sessions. Save project-specific settings for documentation, code analysis, and publishing. 2/5 muse_publish_document Publishes generated documents to external platforms (Notion, GitHub Wiki, Obsidian, Confluence, Slack, or Discord). 3/5 muse_session_history Manages vibe coding session history. Save, retrieve, search, and manage past coding sessions with their code contexts and design decisions. 2/5 muse_session_stats Provides analytics and insights about coding sessions. Actions: overview (summary stats), languages (language breakdown), timeline (activity over t... 2/5 muse_summarize_design_decisions Extracts and analyzes key architectural and design decisions from conversation logs. Supports both English and Korean, with importance scoring and ... 2/5

DESTRUCTIVE TOOLS

2
How many tools does the Vibe Coding MCP server have? +

The Vibe Coding MCP server exposes 15 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Vibe Coding tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Vibe Coding server.

What risk categories do Vibe Coding tools fall into? +

Vibe Coding tools are categorised as Read (2), Write (11), Destructive (2). Each category has a recommended default policy.

Enforce policies on Vibe Coding

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.