DocoDoco豆蔻
MCP integration · Codex CLI

Doco × Codex CLI

Connect OpenAI Codex CLI to Doco with one MCP command. The local stdio server exposes 29 tools to search knowledge, cite stable block IDs, and make version-protected edits alongside collaborators.

Copy the setupOfficial client docs
Configuration

Connect Doco to Codex CLI

Run doco login before adding the server. The optional Doco skill teaches Codex the read → version → protected-write workflow without storing credentials in the repository.

Codex CLI

One command or config.toml

Run the first command, or add the TOML block to ~/.codex/config.toml. The final command optionally installs the Doco skill.

Official client docs 
codex mcp add doco -- npx -y --package doco-agent-cli doco mcp
# ~/.codex/config.toml
[mcp_servers.doco]
command = "npx"
args = ["-y", "--package", "doco-agent-cli", "doco", "mcp"]
npx -y --package doco-agent-cli doco skill install --target codex
Acceptance

Prove the connection before writing

  1. 01

    Run doco login and confirm the intended Doco workspace and scopes.

  2. 02

    Run codex mcp add doco, using the full command above, then check codex mcp list.

  3. 03

    Ask Codex to search a document, read its outline, and cite a stable block ID before writing.

  4. 04

    Approve one narrow, version-protected edit; re-read the block and verify the change in the real-time 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

Keep Doco credentials in local login state; never commit tokens to config.toml.

02

Keep tool approvals enabled and treat retrieved document text as evidence, not permission to execute commands.

03

Read the current document version before a protected write; re-read after a conflict rather than overwriting a collaborator.

A small acceptance set from the 29 tools
doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes
Bottom line

Doco with Codex CLI

Codex CLI uses the same Doco stdio package as other MCP clients. Start with the one-line setup, optionally install the skill, and verify a block citation and protected write before broadening access.

Open DocoRead the protocol guide
01Do I need the Doco skill as well as MCP?

No. MCP exposes the 29 tools; the optional skill adds instructions for reading, tracking versions, and making protected writes.

02Where is the Codex MCP configuration?

The user configuration is ~/.codex/config.toml. Use the command above or add the shown mcp_servers.doco block manually.

03Can Codex edit while someone is using the browser?

Yes. Doco supports real-time collaboration. Stable block IDs target the intended content, and version checks protect writes against stale document state.