Once the [MCP server is connected](/cli/mcp/connect-mcp), your AI client gains a set of **resources** (read-only data) and **tools** (actions) for working with D...
Once the [MCP server is connected](/cli/mcp/connect-mcp), your AI client gains a set of **resources** (read-only data) and **tools** (actions) for working with D...
Once the MCP server is connected, your AI client gains a set of resources (read-only data) and tools (actions) for working with Doxbrix documentation. This page is the reference for all of them.
Resources
Resources are read-only data the assistant can fetch for context:
| Resource | Returns |
|---|---|
| `doxbrix://components` | The full [block catalog](/write/blocks-and-components) with names, props, and examples. |
| `doxbrix://style-guide` | Your workspace's [style and terminology rules](/ai/workspace-ai-policy). |
Reading doxbrix://components before authoring is what lets an assistant use real blocks with correct props instead of guessing.
Discovery tools
| Tool | Description |
|---|---|
| `list_components` | Lists every available Doxbrix block. |
| `get_component` | Returns the props, description, and a usage example for one block. |
Reading tools
| Tool | Description |
|---|---|
| `search_docs` | Full-text [search](/cli/inspect/search-and-quality) across content. |
| `get_page` | Returns a page's content and metadata. |
| `list_pages` | Lists pages with status. |
| `list_projects` | Lists the projects you can access. |
| `ask_ai` | A grounded, cited [answer](/cli/inspect/ai-ask) from your docs. |
Validation tools
The key to correct AI authoring:
| Tool | Description |
|---|---|
| `validate_mdx` | Validates MDX against the real Doxbrix component schema and reports unknown components or props. |
| `quality_check` | Runs a [content-quality scan](/ai/scan-and-content-quality) and returns dimension scores and suggestions. |
A well-behaved assistant calls validate_mdx before writing content to a page, fixing any errors first — so what lands in your docs always passes dxb lint.
Authoring tools
These mutate your project, so use them deliberately:
| Tool | Description |
|---|---|
| `create_page` | Creates a page and wires it into `docs.json`. |
| `update_page` | Updates a page's content. |
| `publish_page` | Publishes a page. |
| `create_space` | Creates a new space. |
| `rename_space` | Renames a space. |
| `move_space` | Moves/reorders a space. |
publish_page puts content live. Keep AI-authored content as drafts you review unless you explicitly want the client to publish.A typical assistant flow
Read doxbrix://components and doxbrix://style-guide.
search_docs and get_page to match existing voice and link related pages.
Compose MDX, then validate_mdx and fix any errors.
create_page to write the validated content as a draft.
Leave publishing to a human review.