MCP tools
Docs pages
Read, search, write, and edit documentation pages through the Doxa MCP docs tools
Overview
The docs pages tools let a connected agent read the structure of a project's docs, read and search pages, write and edit MDX, and upload images. They work on the project's docs branches. Writes to main are rejected through MCP, so create a branch first. See Branches.
The six tools and the OAuth scope each one needs:
| Tool | Purpose | Scope |
|---|---|---|
get_docs_structure | Return the page structure of a project's docs. | docs:read |
read_page | Read the content of one page. | docs:read |
search_docs | Search a project's pages. | docs:read |
write_page | Create or replace a page. | docs:write |
edit_docs | Change existing docs content. | docs:write |
upload_asset | Upload an image for use in pages. | docs:write |
docs:write implies docs:read, so a token with docs:write can also use the read tools. For how scopes are granted and what a client receives when a scope is missing, see MCP Scopes and Approval Requests.
Read and search docs
Start with get_docs_structure to see which pages exist before you read or change them. Then use read_page to fetch one page, or search_docs to find pages that mention a term.
An agent with only docs:read can review and answer questions about your docs without changing them.
Write and edit docs
Use write_page to create a page or replace a page's content. Use edit_docs to change existing docs content. Both tools require docs:write, and both work on a branch, not on main.
Before you let an agent write:
Create a branch for the agent's work. See Branches.
Build a preview and review the branch diff before you publish. See Branches, Previews, Publishing, and Restore.
Publish only after review. Publishing requires the
publishscope. See Publish and history.
Pages use MDX. Components such as Card, Note, Step, Tabs, FileTree, and Mermaid render on published sites. Ask the agent to follow the component syntax described in Note, Step, and Tabs.
Note:
Writes to main are rejected through MCP. If an agent reports that a write was rejected, check that it is working on a named branch.
Upload images
Use upload_asset to add an image to a branch, then reference it from a page. In MDX, use an /assets/ path or an https address, on its own line. Relative paths do not render. See MDX formatting for the page syntax.
Example prompts
Ask your connected agent in plain language, for example:
"List the pages in my docs for project Acme Docs."
"Search my docs for pages that mention webhooks."
"On branch
update-auth, rewrite the authentication page as a numbered procedure.""Upload this diagram to the branch and add it to the getting started page."
The agent chooses the tools. You control which projects and scopes it can use when you approve the connection in Connect an AI Agent with MCP.