Meet Blume: An Open-Source, Zero-Config Documentation Framework That Ships AI-Ready Docs From a Markdown Folder
Blume is an open-source, zero-config documentation framework by OpenAI expert Hayden Bleasel that converts Markdown/MDX folders into production-ready sites using a hidden Astro engine. It features native "AI-Ready" capabilities including `llms.txt` generation, per-page raw Markdown access, and a built-in Model Context Protocol (MCP) server for agent integration. The tool offers a seamless upgrade path via `blume eject`, allowing developers to transition from a managed CLI experience to a standal
Analysis
TL;DR
- Blume is an open-source, zero-config documentation framework by OpenAI expert Hayden Bleasel that converts Markdown/MDX folders into production-ready sites using a hidden Astro engine.
- It features native "AI-Ready" capabilities including
llms.txtgeneration, per-page raw Markdown access, and a built-in Model Context Protocol (MCP) server for agent integration. - The tool offers a seamless upgrade path via
blume eject, allowing developers to transition from a managed CLI experience to a standalone Astro application while retaining core dependencies. - Performance is optimized for Core Web Vitals by shipping no client-side JavaScript in the core theme, relying instead on static HTML rendering.
- It supports diverse content sources (filesystem, Notion, remote MDX), internationalization for 36 locales, and integrates with AI SDKs for in-page chat assistants.
Why It Matters
This release signals a significant shift toward documentation systems that are natively designed for both human consumption and machine readability, addressing the growing need for AI agents to reliably access technical resources. By embedding MCP support and standard AI discovery files (llms.txt) directly into the framework, Blume reduces the friction for integrating documentation into agentic workflows. For practitioners, it offers a low-friction entry point for high-performance docs without the maintenance overhead of custom React-based stacks like Docusaurus.
Technical Details
- Architecture: Blume operates as a CLI wrapper around a hidden Astro project. The CLI scans content into a graph, generates an Astro app in
.blume/, and uses a single catch-all route to render pages via shipped components. - AI Integration: Includes a built-in MCP server exposing four read-only tools (
search_docs,get_page,list_pages,get_navigation) for IDEs like Cursor and VS Code. It also supportsllms.txtflags and in-page AI assistants via the AI SDK. - Performance: The core theme is static-first, shipping zero client-side JavaScript by default, which ensures strong Core Web Vitals scores. Hot reloading is maintained by rewriting only changed files during development.
- Content Management: Supports multiple content sources including local filesystem, Notion databases, and remote MDX. It handles internationalization with locale-aware routing and RTL layout support.
- Extensibility: Developers can use
blume ejectto promote the hidden runtime into a standalone Astro app, gaining full control over the underlying infrastructure while keeping theblumepackage dependency.
Industry Insight
Documentation frameworks are evolving from passive information repositories into active nodes in the AI agent ecosystem. The inclusion of MCP servers and standardized AI discovery protocols suggests that future documentation standards will prioritize machine-readable structures alongside human-friendly UIs. Teams should evaluate their documentation strategies not just for SEO, but for "agent-readability," ensuring their technical assets can be easily ingested by LLMs and coding assistants. Additionally, the trend toward "zero-config" static site generators highlights a demand for reduced operational complexity in developer tooling, favoring solutions that abstract away build pipeline maintenance.
Disclaimer: The above content is generated by AI and is for reference only.