The Doxbrix **MCP server** (`@doxbrix/mcp`) exposes your documentation to AI clients through the [Model Context Protocol](https://modelcontextprotocol.io) — an o...
The Doxbrix **MCP server** (`@doxbrix/mcp`) exposes your documentation to AI clients through the [Model Context Protocol](https://modelcontextprotocol.io) — an o...
The Doxbrix MCP server (@doxbrix/mcp) exposes your documentation to AI clients through the Model Context Protocol — an open standard for connecting AI assistants to tools and data. Once connected, a client like Claude or Cursor can read your block catalog, search and read pages, validate MDX, and author content using the real Doxbrix components — not guessed-at markup.
Why connect the MCP
Without the MCP, an AI assistant has to guess at component names and props — and often invents tags that fail validation. With the MCP connected, the assistant:
- Reads the exact block catalog and props (
list_components,get_component). - Searches and reads your existing pages for context (
search_docs,get_page). - Validates MDX before suggesting it (
validate_mdx), so output is correct. - Follows your style guide via the
doxbrix://style-guideresource.
The server binary
The MCP server installs as @doxbrix/mcp and provides the doxbrix-mcp binary. Most clients launch it for you; you can also run it directly:
npx -y @doxbrix/mcp
# or, if installed globally:
doxbrix-mcpIt authenticates with a Doxbrix token from the DOXBRIX_TOKEN environment variable and serves over stdio for local clients.
Connecting a client
Add the server to your MCP configuration:
{
"mcpServers": {
"doxbrix": {
"command": "npx",
"args": ["-y", "@doxbrix/mcp"],
"env": {
"DOXBRIX_TOKEN": "<your-token>",
"DOXBRIX_PROJECT": "my-docs"
}
}
}
}After adding the config, restart the client. It will list the Doxbrix tools as available.
Authentication
The MCP server reads DOXBRIX_TOKEN from its environment (and DOXBRIX_PROJECT to pick the project). Create a token in Settings → Project → API Tokens — see Authentication.
publish_page. For most authoring workflows, keep generated content as drafts and publish yourself after review.What gets exposed
| Kind | Examples |
|---|---|
| Resources | `doxbrix://components`, `doxbrix://style-guide` |
| Tools | `list_components`, `get_component`, `search_docs`, `get_page`, `validate_mdx`, `create_page`, … |
See Components & validation tools for the full catalog.
Verifying the connection
In your client, ask the assistant to list available Doxbrix components. If the MCP is connected, it returns the real block catalog (Frame, CardGroup, Steps, …). If it can't, recheck the command and token.