Blume vs Docus.The Docus alternative with no Nuxt app.
Docus makes your docs a Nuxt app you configure and extend. Blume turns a folder of Markdown into the whole site, with the llms.txt, MCP server, and assistant Docus users expect, plus API references and versioning, and no app to maintain.
npx blume migrate docus --codex| Blume | Docus | |
|---|---|---|
| You maintain | BlumeA folder of Markdown, plus one optional config file | DocusA Nuxt app: content/, plus app.config.ts and nuxt.config.ts |
| Built on | BlumeAstro, generated and run for you | DocusNuxt 4, Nuxt Content, and Nuxt UI, as a Nuxt layer |
| License | BlumeFree and open source (MIT) | DocusFree and open source (MIT) |
| Agent features | Blumellms.txt, Markdown mirrors, and a JSON API by default; an opt-in MCP server | Docusllms.txt, Markdown pages, agent skills, and an MCP server, on by default |
| AI assistant | BlumeAn in-page assistant on the model you choose, billed by your provider | DocusA built-in assistant on Vercel AI Gateway, or your own AI SDK route |
| API references | BlumeOpenAPI, AsyncAPI, and GraphQL, with a Try it playground | DocusNot built in; an open issue covers adding OpenAPI through Scalar |
| Versioning | Blumeblume version snapshots with a switcher and scoped search | DocusNot built in |
| Languages | Blumeblume translate fills in every locale with your coding agent | DocusBuilt-in i18n through @nuxtjs/i18n, with a folder per locale |
Docus details are from its own pages as of October 7, 2026: Project structure, llms.txt and Markdown, MCP server, Assistant, Internationalization, OpenAPI issue. Something out of date? Let us know
Your docs come with you.MDC becomes MDX, and an agent does the move.
- MDC becomes MDX.
- A bundled codemod turns callouts into
:::directives and cards, steps, tabs, code groups, and fields into Blume components, and makes prose MDX-safe. - Navigation stays in folders.
- Each
.navigation.ymlbecomes ameta.ts, pagenavigationkeys becomesidebar, and sub-navigation sections become header tabs. - Your URLs keep working.
- Both tools strip number prefixes from file names, so most URLs carry over, and
routeRulesredirects and old/raw/Markdown URLs move toredirects. - The assistant and MCP server stay.
- On a server deployment, the agent keeps the assistant on the same model and the MCP server at
/mcp, and publishes yourskills/folder.
Docus
Blume
- app.config.tsblume.config.ts
- .navigation.ymlmeta.ts
- ::caution:::danger
- ::card-group<CardGroup>
- ::field<ResponseField>
- navigation.titlesidebar.label
- "i-lucide-zap""zap"
When Docus might suit you better.Blume isn't the right fit for every team.
- You build with Vue and Nuxt.
- Docus is a Nuxt layer, so your docs can use Vue components in Markdown, Nuxt modules, custom pages, and server routes, or sit inside your existing Nuxt app.
- You want a visual editor.
- Nuxt Studio, a free, self-hostable module, lets teammates edit pages on the live site and commit the changes to Git. Blume is Markdown and MDX in your repo.
- You want your own MCP tools.
- Docus builds its MCP server on the Nuxt MCP Toolkit, so you can add tools, resources, prompts, and extra endpoints in
server/mcp/. Blume's server has a fixed set of read-only tools.
- 1
Run one command in your docs project.
Using Claude Code? Swap
--codexfor--claude. - 2
Review the agent's edits.
It follows Blume's migration playbook for MintlifyFumadocsDocusaurusStarlightNextraGitBookMkDocsReadMeVitePressFernRedoclyVuePressDocsifyDocusmdBookJekyllGitHub Wiki, rewriting your config and pages in place, so you review the whole move as one diff.
- 3
Preview the result.
Run
npx blume dev, then read the agent's summary of anything it dropped or approximated.
Questions, answered.About moving from Docus to Blume.
What's the difference between Blume and Docus?
Docus is a Nuxt layer, so your docs are a Nuxt app: you configure it in app.config.ts and nuxt.config.ts and extend it with Vue components and Nuxt modules. Blume turns a folder of Markdown into the whole site with no app code, and builds in the API references and versioning that Docus leaves out.
Can I keep my Docus content?
Yes. npx blume migrate docus --codex runs a codemod that turns MDC callouts, cards, steps, tabs, and code groups into directives and Blume components, writes each .navigation.yml as a meta.ts, and keeps every old URL working.
Does Blume have an AI assistant and an MCP server like Docus?
Yes, on a server deployment. The agent keeps your assistant on the same model and your MCP server at /mcp, and publishes your skills/ folder under /.well-known/agent-skills/.
Can I still use Vue components?
Yes. Blume renders static HTML with Astro, and a Vue component in islands/ works in any MDX page once you install @astrojs/vue. The agent rebuilds your own content components as Markdown, Blume components, or Vue islands.
What doesn't the migration carry over?
Nuxt UI theme overrides and landing-page decorations, the code-tree file browser and code-preview live rendering, server routes, and your MCP server's own tools and prompts. The agent reports each one so you can decide what to do with it.
Upgrade your docs with Blume.
Install today and ship a production-grade docs site in minutes. Free and open source, forever.
npx blume init