DocoDoco
MCP integration · Cursor

Doco × Cursor

Add Doco to Cursor with the public Directory entry or a project/global mcp.json file. Cursor launches the same stdio package and can search, cite, and update Doco documents through the shared 29-tool contract.

Copy the setupOfficial client docs
Configuration

Connect Doco to Cursor

Use .cursor/mcp.json for a reviewed project configuration or ~/.cursor/mcp.json for a private global setup. The public Cursor Directory entry is also available.

Cursor

Project or global mcp.json

Create .cursor/mcp.json in the repository, or ~/.cursor/mcp.json for all projects. Restart or reload MCP servers after saving.

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 in the same user environment that launches Cursor.

  2. 02

    Add the JSON configuration or install the Doco entry from Cursor Directory.

  3. 03

    Use Cursor MCP status/tool listing to confirm doco is connected and inspect the exposed tool names.

  4. 04

    Start with a read-only token; ask for a document outline and exact block citation before testing one protected write.

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

Review repository .cursor/mcp.json before trusting it; a local stdio server runs commands with your user permissions.

02

Do not paste tokens into committed JSON. Doco's device login keeps credentials in local configuration.

03

Leave normal tool confirmations enabled until the workspace, scopes, and first write have been accepted.

A small acceptance set from the 29 tools
doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes
Bottom line

Doco with Cursor

Cursor is a direct fit for Doco because both the IDE and Cursor Agent understand mcp.json. Install from the Directory for convenience or keep a reviewed project file for reproducibility.

Open DocoRead the protocol guide
01Is Doco listed in Cursor Directory?

Yes. The public Doco plugin entry is searchable in Cursor Directory and contains the stdio MCP configuration.

02Does Cursor need a Doco token in mcp.json?

No. Run doco login locally. Avoid committing tokens or embedding them in project configuration.

03Can Cursor Agent reuse the same configuration?

Cursor Agent detects the same mcp.json configuration and provides CLI commands to list servers and tools.