Docs in your workflow
Author in your own editor and ship from the terminal, no context-switching, no copy-paste, fully scriptable in CI.
CLI & MCP
Write docs from your terminal, or let an AI agent
Author and publish with the dxb CLI: dxb push and you’re live. Or connect the doxbrix MCP server so AI agents can read and update your docs directly.
dxb CLI Local-first authoring MCP for AI agents
How it works
From your terminal to your help center
A docs-as-code workflow that humans and AI agents can both drive.
1. Install the CLIAdd @doxbrix/cli and authenticate in seconds.
2. Author locallyWrite docs in your editor, with docs.json as the source of truth.
3. dxb pushPublish to your branded help center with a single command.
4. Connect MCPLet AI agents read and update docs through the MCP server.
For technical teams
Built for the way developers work
Terminal-native authoring and an agent-ready API, without giving up governance.
dxb push and you’re live
The CLI maps your local structure, syncs orphans, and publishes, so going live is a single, predictable command.
Agent-ready via MCP
The hosted MCP server exposes governed read and write tools, so AI agents can search, draft, and publish within your rules.
FAQ
Common questions
What can the dxb CLI do?
Authenticate, sync your local docs structure, validate and preview, and publish with dxb push. docs.json is the source of truth for structure, and the CLI auto-wires orphaned folders into spaces and groups.
What is the MCP server for?
The doxbrix MCP server lets AI agents and AI-native editors connect to your docs with governed tools, searching content, reading pages, and making approval-aware writes.
Is authoring local-first?
Yes. You can write docs locally in your preferred editor and push them up, keeping your normal git and review workflow intact.
Can I use it in CI?
Absolutely. The CLI is scriptable, so you can validate and publish documentation as part of your existing CI/CD pipeline.