Meet Blume: An Open-Source, Zero-Config Documentation Framework That Ships AI-Ready Docs From a Markdown Folder

Hayden Bleasel, who works at OpenAI, dropped a new open-source project this week called Blume, and it shipped to npm as v1.0.3 the same day it was announced. The pitch is almost aggressively simple: point it at a folder of Markdown or MDX files, run one command, and you get a production-ready documentation site with navigation, search, theming, and even Open Graph images already handled. No app boilerplate to write, no scaffolding to babysit.

Under the hood, Blume is quietly running Astro and Vite. The CLI reads a blume.config.ts file, builds a content graph from your files, then generates a hidden Astro project inside a .blume/ directory that regenerates only the files that changed. That's why hot reload stays snappy while you're editing. The default theme ships zero client-side JavaScript too, which is a deliberate bet on Core Web Vitals scores rather than flashy interactivity. If you outgrow the training wheels, blume eject promotes that hidden Astro app into a standalone project you fully own, though it still leans on the blume package underneath.

What makes this launch feel timely rather than just another static site generator is how hard it leans into AI. Append .md to any page URL and you get raw Markdown back instead of rendered HTML. Flip a flag and Blume spits out llms.txt and llms-full.txt files for crawling agents. There's an optional Ask AI widget wired through the Vercel AI Gateway, OpenRouter, or any OpenAI-compatible endpoint, and Blume can host its own Model Context Protocol server exposing four read-only tools—search_docs, get_page, list_pages, and get_navigation—so tools like Claude Code, Cursor, or VS Code can query your docs directly rather than scraping them.

Beyond the AI hooks, Blume covers the practical stuff teams actually ask for: an OpenAPI-powered interactive API reference with a request playground via Scalar, auto-generated changelogs pulled from GitHub Releases, and support for 36 locales with right-to-left layouts baked in. It can also blend local Markdown with remote content from Notion or Sanity through the same component set, which matters for teams whose docs live in more than one place.

Bleasel is positioning Blume against Mintlify, Docusaurus, and Astro Starlight, and the comparison is mostly favorable on paper: MIT-licensed, static-first, built-in MCP support, and an eject path that keeps you from getting locked in. The catch is that it needs Node.js 22.12 or newer, some features like Ask AI require a server rather than pure static hosting, and being three days old means the plugin ecosystem and community support that mature tools like Docusaurus have accumulated just aren't there yet. Early adopters like Quiver, migrating off Mintlify, and Neon's MCP docs suggest real teams are already willing to bet on it anyway.