Developer tools#Site building#MCP
nimbus: Cloudflare's docs framework that publishes for humans and agents
Cloudflare's Astro docs framework publishes one MDX source as HTML for people and Markdown plus llms.txt for agents, with checks and optional MCP output. MIT.
Project facts
GitHub Ecosystem- License
- MIT
- Language
- TypeScript
- Stars
- 1,723
- Data checked
- 2026-11-04
Snapshot figures reflect the check date and may change over time.
Docs for AI agents have a format problem: people want HTML, agents want Markdown, and keeping both in sync drifts. nimbus — recommended by vikingmute on November 4, 2026 — is Cloudflare’s open-source answer (MIT, TypeScript, 1,723 stars as of November 4): an Astro-based authoring tool that turns the split into one pipeline. You write MDX as usual; the build publishes HTML for readers and Markdown versions for agents, alongside llms.txt and llms-full.txt — a framework-shaped version of what this site maintains by hand for search and AI citation.
Core features
- Dual-format publishing: Markdown versions of docs and API reference pages plus
llms.txtandllms-full.txt; hidden versions stay out of the agent artifacts. - Writing components: MDX components for code blocks, tabs, steps, cards, file trees, reusable snippets and interactive diagrams, some installed on demand with
nimbus-docs add; API reference generated from OpenAPI 3.x with multiple versions. - Content checking: config, frontmatter and MDX components validated at build;
lintreports authoring mistakes without blocking the build;checkinspects environment, structure, content and types without building —--fixapplies safe fixes and--jsonhands findings straight to an agent. - Optional agent output: Agent Skills, WebMCP search and a remote MCP server turn the docs into something agents can call directly.
- Extended sources: pages can load from other Git repositories or Notion, with docs versions and search built in.
Typical use cases
- Open-source project docs: one source serving human readers and the coding agents that come to query it — the README’s own line is “docs for humans and agents”.
- API documentation sites: OpenAPI generation with versioning; agents read the Markdown version far more accurately than scraped HTML.
- Team knowledge bases: pull Notion content into a unified site, and let
check --jsonkeep documentation quality agent-maintained.
Quick start
Requires Node.js 22.12+:
npx @cloudflare/create-nimbus-docs@latest my-docs --yes --package-manager npm
cd my-docs && npm run dev
Pages live in src/content/docs/ as MDX; a static npm run build hosts anywhere, and server-needing features like the remote MCP server take a Cloudflare, Netlify, Vercel or Node adapter.
Summary
nimbus fits project docs and API doc teams serving both human and agent readers; internal wikis and Notion-style WYSIWYG teams won’t feel at home — it assumes you’re happy writing MDX in a repo. Facts and limits: MIT, TypeScript, and the scaffolder copies the whole site into your repo where any part is editable; it is Pre-1.0 and the public API can change between minor releases, so pin versions and read changelogs. The bet matches this site’s own: your documentation’s next big reader is not a person but an agent with a task — so ship the Markdown, the llms.txt and the MCP interface together. For the other half of agent information access, see our research piece on agent-browser-control.