Author MCP

Pro

Build your docs out loud.

Hook Claude Code, Cursor, Codex, or any MCP-capable agent up to your Docsio site. Describe the change in plain English, your agent drafts it, shows you the diff, and publishes when you say go. Never open the Docsio UI unless you want to.

Get Started Free
claude — docsio-docs
Claude CodeClaude Code 1.4.2 · connected to docsio-docs-author
>Our webhooks now retry for 48 hours instead of 24. Update the webhooks page and publish.
·I'll pull the webhooks page, swap the retry window, diff it against what's live, and publish after you confirm.
docsio-docs-author::read_page → docs/features/webhooks.md, 612 words
docsio-docs-author::write_page → updated 2 paragraphs, 614 words
docsio-docs-author::get_unpublished_changes → 1 modified, 0 added, 0 deleted
·Diff summary:

Retry behavior — changed "up to 24 hours" to "up to 48 hours" in the failure policy section. Added a sentence noting the longer window applies to all webhook events, not just payment failures.

>Looks right. Publish.
docsio-docs-author::publish → v4 live in 52s
•Shipped. Live at docsio.docs.docsio.co/docs/features/webhooks
>Also scrape the last 3 changelog entries from our site and add a What's New page

Why this matters

Docs fall out of date because writing them breaks flow.

Every shipped feature should come with a doc update. In practice it doesn't, because context-switching out of your IDE to log into a docs tool, navigate to the right page, and paste an update is just enough friction to push it to "later." Later rarely happens.

The Author MCP closes the loop. You're already in Claude Code or Cursor when you ship a feature. Your agent already knows what changed. Tell it to update the docs — it reads what's there, drafts the edit, and publishes on your word. No tab switch, no mental state lost.

That's what we mean by "build your docs out loud." You talk; your docs update.

Capabilities

Everything your agent needs to ship confident updates

Read before it writes

Every edit starts with your agent pulling the current page so it doesn't overwrite what's there. No blind rewrites, no lost context.

Writes land in draft

Every change goes to your project's draft state. Your public site doesn't move until you explicitly call publish. You can always back out.

Scrape sources into docs

Your agent can pull markdown from any URL — changelogs, release notes, API specs — and fold the content straight into a new or existing page.

Publish on your word

When the draft looks good, tell your agent to publish. Docsio rebuilds your site, deploys to Vercel, and reports the live URL back.

Validation baked in

The same guardrails the Docsio editor agent uses: em dashes stripped, category names sanitized, escaped newlines fixed. Broken sites are hard to ship.

Revokable in one click

Tokens live in your project settings. Lose a laptop, revoke the token. Rotating them is a button press.

Tool surface

16 tools, grouped by job.

Your agent gets the same editing vocabulary as the in-app AI agent. The only thing missing is the live preview — because you're in your IDE.

Read & discover

list_pages

Every page with title, slug, category, word count.

list_project_structure

Full file tree of docs, assets, config.

read_page

Pull the full markdown of any page.

search

Full-text search across the site.

get_project_info

Name, description, live URL, last publish.

Mutate content

write_page

Create or update a page. Validation applied.

create_page

New page with proper frontmatter + slug.

delete_page

Remove a page from the draft.

rename_page

Change a page's slug in place.

upload_asset

Drop an image into the static directory.

update_project_info

Rename the project, edit its description.

Pull in external content

scrape_url

Pull any URL as markdown.

map_site

List every URL on a site.

batch_scrape

Scrape up to 20 URLs at once.

Review & ship

get_unpublished_changes

Diff of every draft change vs live.

publish

Build and deploy to Vercel. Rate-limited.

Setup

Three steps. Under a minute.

  1. 1

    Upgrade the site to Pro.

    Author MCP is a Pro feature. $60/month per site, no per-call pricing.

  2. 2

    Generate a token.

    Project Settings → MCP → Author MCP → Create token. The raw value appears once; copy it into your MCP client config.

  3. 3

    Talk to your agent.

    Run claude mcp add --scope project --transport http ... (or the equivalent for Cursor, Codex, etc.) and tell your agent what to change.

FAQ

Common questions

Is this different from the AI editing agent inside Docsio?

Yes. The in-app agent lives in Docsio's editor and runs in a live sandbox with a preview. The Author MCP is headless — it talks to Claude Code, Cursor, or any MCP client on your machine, writes to your project's draft, and publishes on command. Same editing power, no browser tab required.

Which clients are supported?

Anything that speaks the MCP HTTP transport. Tested with Claude Code, Cursor, VS Code (Copilot), OpenAI Codex, and Antigravity. The connection snippets for each live in project settings.

Can the agent break my live site?

No. Every edit writes to your project's draft. The live site stays on its last published build until your agent runs the publish tool. If a publish breaks something, version history lets you roll back.

What happens if a tool call fails?

You get a structured error the agent can narrate back to you in plain English. Auth failures, plan downgrades, rate limits, validation errors — all surface as readable messages, not crashes.

How is this priced?

Author MCP is included in Pro ($60/month per site). Same price as the rest of Pro — no per-token billing, no per-call metering.

What if I don't have a public site yet?

You still need a Docsio project. Generate one from your product URL or uploaded documents, then connect the Author MCP to keep it updated as your product evolves.

Your next docs update can happen without opening a browser.

Start free. Upgrade a site to Pro when you're ready to wire up the Author MCP.

Get Started Free

Headless editingNatural language inPublish on command