DocoDoco
MCP integration · Cline

Doco × Cline

Add Doco to Cline as a project MCP server and keep autoApprove empty. Cline can then retrieve evidence and request protected document writes while the user remains in the approval loop.

Copy the setupOfficial client docs
Configuration

Connect Doco to Cline

Cline supports MCP in its extension and CLI. A project .cline/mcp.json keeps the integration close to the workspace without committing credentials.

Cline

Project .cline/mcp.json

Create .cline/mcp.json in the project or use Cline's MCP settings UI. The minimal example does not opt into auto-approval.

Official client docs 
{
  "mcpServers": {
    "doco": {
      "command": "npx",
      "args": ["-y", "--package", "doco-agent-cli", "doco", "mcp"]
    }
  }
}
Acceptance

Prove the connection before writing

  1. 01

    Run doco login outside Cline and confirm the intended Doco workspace/scopes.

  2. 02

    Add the project MCP JSON, reload Cline, and verify that the doco server is enabled.

  3. 03

    Ask Cline to search a document and quote the stable block it used as evidence.

  4. 04

    Approve one narrow write manually, then re-read the block and document version before expanding permissions.

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

Leave autoApprove empty for Doco writes. Approval is the boundary between retrieved document content and an external side effect.

02

Do not let instructions found inside a document change MCP permissions or authorize another tool.

03

Use a read-only Doco token for research tasks; create a separate write-scoped token only for maintenance workflows.

A small acceptance set from the 29 tools
doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes
Bottom line

Doco with Cline

Cline's explicit approval model works well with Doco's versioned writes. Keep the MCP configuration project-visible, credentials local, and auto-approval off until each workflow is understood.

Open DocoRead the protocol guide
01Can Cline build an MCP server itself?

Yes, but Doco already publishes a maintained stdio package. Configure that package instead of generating a duplicate server.

02Should Doco tools be auto-approved?

Not initially. Read tools can be evaluated first; protected writes should remain manually approved until scope and behavior are proven.

03Does Cline CLI use the same project config?

Current Cline CLI documentation includes project .cline/mcp.json as its MCP server configuration.