The documentation tool Claude can actually use

Why Claude needs a documentation tool, not just a chat window

Most teams already use Claude to draft documentation. The trouble starts after the draft. The text lives in a chat, someone copies it into a wiki, the formatting breaks, and a month later nobody knows which version is current. Claude is good at writing; on its own it has no place to keep a docs site organized, versioned and published.

A Claude documentation tool closes that gap. Instead of copying and pasting, Claude works directly inside the system where your docs live. OpenDocs connects to Claude through the Model Context Protocol (MCP), so Claude can read your existing pages, search them, create new ones, reorganize the tree and publish, all from the same conversation where you asked for the change.

What Claude can do inside OpenDocs

Once connected, Claude uses a set of named tools. The reading tools let it list your spaces, read a space’s navigation tree, open any page as Markdown, run a full-text search that includes drafts, look at a page’s edit history and check which translations are out of date. On Enterprise, it can also read reader traffic and search terms.

The editing tools let it create a space, create a page from Markdown or a template, replace a page’s content, rename a page or change its slug (old slugs redirect automatically), move a page in the tree, publish pages or a whole space, and roll a page back to an earlier revision. The full list, with what each tool does, is on Use OpenDocs with Claude.

In practice that means requests like these just work:

• “Draft a getting-started page for our API in the Guides space.”
• “Find pages that mention the old pricing and update them.”
• “Restore yesterday’s version of the Setup page.”
• “Translate the Setup page into Spanish and Portuguese, then publish it.”

Every change is reviewable

Handing a docs site to an AI model only makes sense if you can see and undo what it did. In OpenDocs, every edit Claude makes is saved as a page revision authored Claude (MCP). You can compare it with the previous version and restore any earlier revision. Before Claude replaces a page’s text, a snapshot of the current content is kept, so nothing is lost.

Tools that remove or replace content, such as deleting a page, replacing its text or taking a space offline, are ones Claude asks about before using. Claude also acts only inside the organization you chose when you connected it, and only with your role’s permissions: a Viewer can only read.

Three ways to work with Claude

In claude.ai or Claude Desktop

OpenDocs is listed in Claude’s connector directory. Choose Connect, sign in to OpenDocs, pick your organization and allow read-only or read-and-edit access. This works on every plan, including Free, and you can disconnect at any time.

In Claude Code

Developers can add OpenDocs as an MCP server in Claude Code with an OpenDocs API key, then ask Claude to document the repository they are working in. The OpenDocs plugin adds skills for that job: turning a repo into a docs site, publishing from a conversation, writing SOPs and auditing a space. API keys require an Enterprise or Compliance plan. Setup commands are on OpenDocs for Claude Code.

For your readers

Every public docs site on a paid plan also answers MCP at its address plus /mcp. Your customers can add your docs to their own Claude and get answers that link back to the exact page, with no sign-in and read-only access to what is already public.

What you get beyond the writing

A documentation tool is more than an editor. OpenDocs includes a visual block editor for people who prefer to write by hand, built-in SEO and version history on every plan; two-way GitHub Sync, custom domains and custom themes on Pro; and AI translation into 38 languages using your own Anthropic API key. Analytics, PDF and Markdown export, the REST API and audit logs are part of Enterprise. Teams in regulated industries can use the Compliance plan for controlled documents with review and approval sign-off and read acknowledgments.

Readers are always free. You pay only for the members who edit and manage documentation.

How to start

1. Create a free OpenDocs account. Every account starts with a 14-day Pro trial, no card required.
2. Connect OpenDocs from Claude’s connector directory, or add it to Claude Code with an API key.
3. Ask Claude to create a space and draft your first pages. Review them, then ask Claude to publish.

If you want a guided walkthrough, the Claude guides cover publishing from a chat, writing SOPs, building a help center and a library of prompts for documentation work. When you are ready to choose a plan, compare them on the pricing page.