Connect OpenDocs
Add OpenDocs to Claude Code as an MCP server, using an OpenDocs API key created by an organization Admin or Owner in Settings > API.
Turn the repository you are working in into a documentation site without leaving your terminal. Claude Code reads your code, writes the pages into OpenDocs as drafts, and publishes only when you ask.
Free plan forever. 14-day Pro trial, no card.
How it looks
Ask in plain words. Claude proposes an outline, you confirm it, and the pages land in OpenDocs as drafts. Nothing goes live until you say so.
> Document this repo in OpenDocs
Reading README.md, CHANGELOG.md, package.json and src/
Proposed space: Acme CLI
Getting started overview, installation, quickstart
Guides one page per task
Reference configuration, CLI commands
Troubleshooting common errors, FAQ
Create these pages as drafts?
> Yes, go ahead
✓ list_spaces
✓ create_space Acme CLI
✓ create_page 12 drafts
12 draft pages are ready to review. Tell me when to publish.
> Publish it
✓ publish_pages
✓ publish_space
Published. Every change is saved in page history.
Setup
Connect OpenDocs, add the plugin, then give your customers a read-only connection to the docs you publish.
Add OpenDocs to Claude Code as an MCP server, using an OpenDocs API key created by an organization Admin or Owner in Settings > API.
Add the OpenDocs plugin marketplace, then install the plugin. It gives Claude four documentation skills that use the OpenDocs tools.
Every public docs site on a paid plan answers MCP at its address plus /mcp. Your readers add it to their own Claude, read-only, with no sign-in.
Step 1: connect OpenDocs (replace od_YOUR_KEY with your API key)
claude mcp add --transport http opendocs https://app.opendocs.cloud/mcp --header "Authorization: Bearer od_YOUR_KEY"
Step 2: inside Claude Code, add the plugin marketplace
/plugin marketplace add P4Software/opendocs-claude-plugin
Then install the plugin
/plugin install opendocs@opendocs
Step 3: what your readers run (your docs address plus /mcp)
claude mcp add --transport http docs https://docs.yourcompany.com/mcp
Prefer the browser? The same plugin installs in claude.ai under Customize > Plugins > Add > Add marketplace, and the OpenDocs connector is in Claude’s connector directory on every plan. See Use OpenDocs with Claude.
The plugin
The OpenDocs plugin contains instructions only: it stores nothing and runs no code. Claude shows drafts before saving and publishes only when you ask.
Turns the repository in your working directory into a docs site: getting started, guides, reference and troubleshooting. It reads your README, manifest, public surface and tests, confirms the outline with you first, and never reads or quotes .env files or credentials.
“Document this repo in OpenDocs”
Publishes something from the conversation, such as a policy, help article or release notes, as a page in the right space. If a page on the same topic exists, it offers to update it instead of creating a duplicate.
“Publish these release notes to our docs”
Writes a standard operating procedure in a consistent structure (purpose, scope, roles, numbered steps, records, revision history) and saves it to OpenDocs. Anything you did not confirm is marked “To confirm”.
“Write an SOP for our release process”
Reviews a docs space for missing, stale or hard-to-use pages and ranks what to fix. Where your plan includes analytics, it also checks reader searches that found nothing. It never deletes pages without explicit confirmation.
“Audit our Developer Docs space”
Safety
Claude only acts inside the OpenDocs organization it is connected to, and only with the permissions that connection has. Every edit is saved as a page revision authored Claude (MCP), so you can see exactly what changed and restore any earlier version.
Before Claude replaces a page’s text, OpenDocs keeps a snapshot of the current content. Tools that remove or replace content, such as update_page_content, unpublish_space and delete_page, are ones Claude asks about before using.
Claude Code connection: API keys require an Enterprise or Compliance plan. claude.ai and Claude Desktop: the OpenDocs connector works on every plan, including Free, and you sign in with OAuth. Reader connection for your customers: every public docs site on Pro, Enterprise and Compliance, and during the 14-day Pro trial; not on the Free plan. See pricing for everything each plan includes.
No. Once OpenDocs is connected as an MCP server, Claude Code can already use the OpenDocs tools. The plugin adds four skills that give Claude a consistent way to document a repository, publish from a conversation, write SOPs and audit a docs space.
Claude Code connects with an OpenDocs API key, and API keys require an Enterprise or Compliance plan. An organization Admin or Owner creates them in Settings > API. The claude.ai and Claude Desktop connector works on every plan, including Free.
No. The plugin creates pages as drafts, shows you the outline and drafts first, and publishes only when you ask. Every change is saved in page history, so you can restore an earlier version.
The repo-to-docs skill tells Claude never to read or quote .env files, credentials, keys, tokens or anything under a secrets folder, and never to put such values in a page.
Only what is already public: published pages in public spaces, read-only. Drafts, unlisted and private spaces are never shared. It is on for public spaces by default, and you can turn it off per space under Claude in the space settings.
Yes. In claude.ai, open Customize > Plugins > Add > Add marketplace and enter the plugin repository URL. The skills then work with the OpenDocs connector you add from Claude’s connector directory.
Independence notice: OpenDocs is an independent product by Grupo Barrdega. It is not affiliated with or endorsed by Anthropic. Claude and Claude Code are trademarks of Anthropic.
Start on the Free plan, or try every Pro feature for 14 days with no card. After 14 days you continue free on 1 space, or upgrade.