Five ways OpenDocs integrates with Claude

One documentation platform, several Claude integrations

“Integrating Claude with your docs” can mean different things. A writer may want Claude to draft and publish pages from a chat. A developer may want Claude Code to document a repository. A support lead may want customers to ask Claude questions and get answers from the help center. And an editor may simply want AI help while writing. OpenDocs supports each of these, and they share one principle: Claude works on your real, published documentation, and every change is saved in page history.

Below are the five integration points, how each one authenticates, and what it can and cannot do.

1. The connector for claude.ai and Claude Desktop

OpenDocs is listed in Claude’s connector directory. You choose Connect, sign in to OpenDocs with OAuth, pick the organization Claude may access and allow read-only or read-and-edit access. You can also add it as a custom connector with the URL https://app.opendocs.cloud/mcp.

Claude can then list spaces, read the page tree, read and search pages including drafts, check translation status, create and edit pages, move them, publish them and restore earlier revisions. It acts with your role’s permissions, so a Viewer can only read. Plan: every plan, including Free.

2. Claude Code over MCP

The same MCP server is available to Claude Code, authenticated with an OpenDocs API key instead of OAuth:

claude mcp add --transport http opendocs https://app.opendocs.cloud/mcp --header "Authorization: Bearer od_YOUR_KEY"

This is the integration for developers who want documentation to come from the code: Claude Code reads the repository and writes the pages into OpenDocs. API keys are created by an organization Admin or Owner in Settings > API. Plan: Enterprise or Compliance. Full setup is on OpenDocs for Claude Code.

3. The OpenDocs plugin

The OpenDocs plugin adds four skills that tell Claude how to do common documentation jobs well: repo-to-docs turns a repository into a docs site, publish-to-opendocs turns something from the conversation into a page, write-sop writes standard operating procedures in a consistent structure, and docs-audit reviews a space for missing and stale pages. The plugin contains instructions only; it stores nothing and runs no code. It uses the tools of whichever OpenDocs connection you have set up, in Claude Code or in claude.ai.

4. A reader connection for your customers

Every public docs site on a paid plan also answers MCP at its address plus /mcp, for example https://docs.yourcompany.com/mcp. This is separate from the editor connection: it is read-only, needs no sign-in and gives no access to your OpenDocs account. Your customers add it to their own Claude, and Claude can list your public spaces, read the table of contents, search and read full pages, then link its answers back to the exact page.

Only published pages in public spaces are shared. It is on for public spaces by default, and you can turn it off per space. Plan: Pro, Enterprise and Compliance, and during the 14-day Pro trial; not on the Free plan. The reader connection guide covers the details.

5. AI writing and translation with your own Anthropic key

Inside the OpenDocs editor, the AI Write Assistant, AI Writer Improver and AI Translations are powered by Claude. They use your own Anthropic API key: you connect the key in your settings and pay Anthropic directly for usage, with no markup, credits or per-answer fees from OpenDocs. AI Translations cover 38 languages, so a page written once can serve readers in their own language.

Security and control across every integration

• Scoped access. The editor connections act only inside one organization and within the permissions they were given. The reader connection only reads what is already public.
• Full history. Every edit Claude makes is saved as a page revision authored Claude (MCP), and any earlier revision can be restored.
• Confirmation before destructive changes. Tools that remove or replace content are ones Claude asks about before using, and a snapshot is kept before a page’s text is replaced.
• Easy to disconnect. Remove the connector in claude.ai, or in OpenDocs under Settings > Connected apps.

Which integration should you start with?

If your team writes in chat, start with the connector: it is free on every plan and takes a minute to set up. If your documentation lives next to your code, add Claude Code and the plugin. If your customers already use Claude, turn on the reader connection so they get answers from your docs instead of guesses. Step-by-step walkthroughs for each are in the Claude guides, and the pricing page shows what every plan includes.