Most people assume MarkdownAI works like this: Claude reads a rendered MarkdownAI file and acts on it. That’s not what happens. Yes, MarkdownAI can parse and render a .md file into a result - and that’s perfectly useful if you’re using it as a CLI tool. But that’s not why it’s called Markdown AI . The reason it’s called MarkdownAI - and where the real power comes from - is the MCP server, the hooks, and the phase design. Here’s what actually happens: Claude requests a .md file. The MarkdownAI MCP server intercepts that request. Instead of dumping the whole rendered file into context, it reads the document, identifies the current phase, and hands Claude only what it needs for that phase - exactly like a human would prompt it. Claude never sees the whole document. It only gets the current phase plus its constraints. This means Claude is always aligned - it only knows what it should know, and it’s always working within the boundaries defined for that phase. This means: Massive token savings - Claude isn’t processing 890 pages of documentation on every request No stale context - each phase is executed fresh with live data No hallucination about what exists - the runtime tells Claude exactly what’s there Always aligned - constraints are delivered with every phase, not assumed The power isn’t the markdown format. The power is the MCP server turning a document into a live, phase-aware, always-aligned conversation between Claude and your codebase. That’s MarkdownAI. GitHub: https://github.com/TheDecipherist/markdownai npm: https://www.npmjs.com/package/@markdownai/markdownai And a big thank you to all the people that have opened issues and tried MarkdownAI! submitted by /u/TheDecipherist
Originally posted by u/TheDecipherist on r/ClaudeCode
You must log in or # to comment.