DocoDoco豆蔻
MCP integration · VS Code Copilot

Doco × VS Code Copilot

Connect GitHub Copilot in VS Code agent mode to Doco. Search shared documents, cite stable block IDs, and request version-protected writes while teammates collaborate in real time.

Copy the setupOfficial client docs
Configuration

Connect Doco to VS Code Copilot

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

VS Code Copilot

Workspace config or portable Agent Host config

Put the server in .vscode/mcp.json for the current workspace. For a config shared directly with Agent Host and other Copilot tools, use workspace .mcp.json or ~/.copilot/mcp-config.json.

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

Prove the connection before writing

  1. 01

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

  2. 02

    Run MCP: List Servers, review the command, and confirm trust before starting it.

  3. 03

    Ask Copilot in agent mode to search a document and cite a stable block ID from a read-only result.

  4. 04

    Confirm one narrow, version-protected write, then re-read the block and verify it in the Doco 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

Run MCP: List Servers, review the command, and confirm trust before starting it.

02

Keep login credentials outside MCP configuration and review project configuration before loading it.

03

Document content cannot authorize tool calls. Read the current version and resolve conflicts before retrying a write.

A small acceptance set from the 29 tools
doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes
Bottom line

Doco with VS Code Copilot

Put the server in .vscode/mcp.json for the current workspace. For a config shared directly with Agent Host and other Copilot tools, use workspace .mcp.json or ~/.copilot/mcp-config.json.

Open DocoRead the protocol guide
01Where should I put the MCP configuration?

Put the server in .vscode/mcp.json for the current workspace. For a config shared directly with Agent Host and other Copilot tools, use workspace .mcp.json or ~/.copilot/mcp-config.json.

02How do I start the Doco server?

Run MCP: List Servers, review the command, and confirm trust before starting it.

03Do I need a Doco token in the JSON?

No. Run doco login locally in the environment that launches VS Code. Keep credentials out of shared project configuration.