Auto-document vibe coding sessions - collect, summarize, and publish
MCP server that automatically collects, summarizes, documents, and publishes code and design decisions created during vibe coding sessions. This MCP server provides 15 tools for managing vibe coding documentation: ------|-------------| | Collects code blocks and conversation summaries into structured context | | Extracts key architectural and design decisions from conversation logs | | Generates…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
muse_analyze_codeNo description publishedThis tool published no description. Forge does not invent one.
muse_auto_tagNo description publishedThis tool published no description. Forge does not invent one.
muse_batchNo description publishedThis tool published no description. Forge does not invent one.
muse_collect_code_contextNo description publishedThis tool published no description. Forge does not invent one.
muse_create_session_logNo description publishedThis tool published no description. Forge does not invent one.
muse_export_sessionNo description publishedThis tool published no description. Forge does not invent one.
muse_generate_dev_documentNo description publishedThis tool published no description. Forge does not invent one.
myFunctionNo description publishedThis tool published no description. Forge does not invent one.
muse_gitNo description publishedThis tool published no description. Forge does not invent one.
muse_normalize_for_platformNo description publishedThis tool published no description. Forge does not invent one.
muse_project_profileNo description publishedThis tool published no description. Forge does not invent one.
muse_publish_documentNo description publishedThis tool published no description. Forge does not invent one.
muse_session_historyNo description publishedThis tool published no description. Forge does not invent one.
muse_session_statsNo description publishedThis tool published no description. Forge does not invent one.
muse_summarize_design_decisionsNo description publishedThis tool published no description. Forge does not invent one.
muse_templateNo description publishedThis tool published no description. Forge does not invent one.
0 of 16 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server that automatically collects, summarizes, documents, and publishes code and design decisions created during vibe coding sessions. This MCP server provides 15 tools for managing vibe coding documentation: ------|-------------| | Collects code blocks and conversation summaries into structured context | | Extracts key architectural and design decisions from conversation logs | | Generates README, DESIGN, TUTORIAL, CHANGELOG, API, or ARCHITECTURE documents | | Converts Markdown documents…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.