MCP integration · Windsurf Cascade

Doco × Windsurf Cascade

Connect Windsurf Cascade to Doco by adding the stdio package to its MCP settings or raw mcp_config.json. Cascade then discovers Doco's tools for structured, version-protected knowledge work.

Copy the setup Official client docs

Configuration

Connect Doco to Windsurf Cascade

Windsurf supports stdio, Streamable HTTP, and SSE. This guide uses local stdio so Doco's device login and CLI configuration stay on your machine.

Windsurf Cascade

Raw mcp_config.json

Open Windsurf Settings → Cascade → MCP Servers, or edit ~/.codeium/windsurf/mcp_config.json and reload the server.

Official client docs

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

Acceptance

Prove the connection before writing

01
Run doco login and keep the resulting credential in the local Doco config.
02
Add the doco server to Windsurf MCP settings or the raw configuration file.
03
Open the MCP panel, enable only the Doco tools needed for the task, and verify connection state.
04
Ask Cascade to search and cite a block; test a protected write only after the read path is correct.

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

Cascade has a total enabled-tool limit, so disable unused tools or servers instead of exposing everything at once.

02

Keep approval controls on for writes; a successful connection is not permission to mutate arbitrary documents.

03

Use environment interpolation for any headless credential and never put a literal token in shared JSON.

A small acceptance set from the 29 tools

doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes

Bottom line

Doco with Windsurf Cascade

Windsurf can launch Doco as a standard local MCP server. The main operational choice is tool discipline: expose the small set needed for the current workflow and retain write confirmations.

Open Doco Read the protocol guide

01Where does Windsurf store MCP settings?

The raw configuration is ~/.codeium/windsurf/mcp_config.json, and the same settings are accessible from the Cascade MCP panel.

02Can Windsurf use Doco's remote HTTP endpoint?

Windsurf supports Streamable HTTP, but Doco's remote endpoint currently uses caller-provided API tokens. The local stdio path is simpler for browser device login.

03Why not auto-enable all 29 tools?

A smaller active tool set reduces ambiguity and keeps the permission boundary visible. Enable writes only for workflows that require them.