DocoDoco
MCP integration · Claude Code

Doco × Claude Code

Connect Claude Code to Doco with one stdio MCP command, or install the Doco plugin to bundle the same 29-tool server with the read → version → protected-write operating skill.

Copy the setupOfficial client docs
Configuration

Connect Doco to Claude Code

The bare MCP command is the smallest setup. The plugin adds operating guidance without putting your Doco token in the repository.

Claude Code

One command or one plugin

Run the command in a terminal. Use --scope project only if the team has reviewed the shared .mcp.json configuration.

Official client docs 
claude mcp add doco -- npx -y --package doco-agent-cli doco mcp
/plugin marketplace add songofhawk/doco
/plugin install doco@doco
Acceptance

Prove the connection before writing

  1. 01

    Run doco login and approve only the scopes this Claude Code session needs.

  2. 02

    Add the stdio server, then run claude mcp list or open /mcp and confirm that doco exposes tools.

  3. 03

    Ask Claude to list knowledge bases, open one document, and cite a stable block before granting write scope.

  4. 04

    For the first write, change one disposable block and confirm the new version in both MCP output and the browser editor.

Permission boundary

Start read-only, keep confirmations

The MCP process runs with your user permissions and Doco token. Review the command, expose only the intended workspace, and grant write scope only after read-only acceptance succeeds.

01

Prefer the plugin when you want the safe-write protocol loaded consistently; use bare MCP when you want the smallest configuration.

02

Keep project-scoped MCP approval enabled. External document content can contain prompt injection and must not authorize tool use.

03

Never commit Doco tokens. The CLI stores login state locally; headless tokens belong in protected environment variables.

A small acceptance set from the 29 tools
doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes
Bottom line

Doco with Claude Code

Claude Code has the smoothest Doco path: a one-line MCP command and a repository plugin. The important acceptance test is not that /mcp says connected; it is that Claude can cite a block, respect a version, and verify its write.

Open DocoRead the protocol guide
01Should I install the plugin or only MCP?

Both start the same Doco MCP server. The plugin also bundles the operating skill; bare MCP is sufficient when your own instructions already enforce safe reads and writes.

02Where is the MCP configuration stored?

Claude Code supports local, project, and user scopes. Project scope writes .mcp.json and requires approval before use.

03Can Claude Code use Doco in cloud sessions?

Repository .mcp.json can be available in cloud sessions, but credentials need an explicitly managed environment. Do not commit static tokens.