Overview
Docsio ships two MCP servers per project. Each has a different audience.
Reader MCP — for your end-users Pro
Public, read-only. The URL of your reader MCP is what you give to developers building on top of your product. They plug it into Claude Code, Cursor, or any MCP-capable agent and it gives those tools direct access to your docs.
Three tools exposed:
search_docs(query)— keyword search across all your pages with snippets.get_page(slug)— full markdown of a specific page.list_pages(category?)— list all pages, optionally filtered by category.
Visit any project that has it enabled and you'll see a copy-pasteable config snippet for every major MCP client.
Author MCP — for you, the docs owner Pro
Private, token-authenticated. Generate a token on a per-project basis, paste it into your AI tool's config, and the tool can read, write, scrape, and publish your docs as you.
Sixteen tools, including:
- All read tools (project info, pages, structure, search)
write_page,create_page,delete_page,rename_pagescrape_url,map_site,batch_scrapeget_unpublished_changes,publish,get_publish_status
Effectively, Author MCP lets you edit your docs from Claude Code without ever opening Docsio.
How they're different
| Reader MCP | Author MCP | |
|---|---|---|
| Who uses it | Your end-users | You |
| Auth | None (public) | Per-project token |
| Permissions | Read-only | Read + Write + Publish |
| Plan | Pro | Pro |
| Tools | 3 | 16 |
| Where you get the URL | Project settings → MCP | Project settings → MCP → Author MCP → Generate token |
Why both?
A reader MCP lets your customers integrate your docs into their AI tools — "hey Claude, how do I auth with Acme's API?" → Claude pulls the answer from your docs. That's a customer-facing feature.
An author MCP lets you edit your own docs from your IDE. No more switching tabs to Docsio to fix a typo — "Claude, fix this typo on the install page and publish." That's a productivity feature.
Setup
Both setups are the same shape: Docsio gives you a copy-pasteable config snippet, you paste it into your MCP tool's config file, restart the tool, the tool sees the server.
Detailed setup snippets for Claude Code, Cursor, VS Code, Codex, and Antigravity in Setup snippets.
What MCP is, briefly
MCP (Model Context Protocol) is a standard way for AI tools to talk to external services. Anthropic introduced it in late 2024; everyone (Claude Code, Cursor, OpenAI Codex, Cody, Continue, etc.) supports it now. Each MCP server exposes a set of "tools" the AI can call. Tools have schemas, the AI knows when to call which.
You don't need to understand the protocol details to use Docsio's MCP servers — just paste the snippet, the tool figures out the rest.