MCP integration · Continue

Doco × Continue

Connect Continue to Doco through its YAML mcpServers configuration, or place compatible JSON inside .continue/mcpServers. The same stdio process gives Continue structured access to Doco knowledge.

Copy the setup Official client docs

Configuration

Connect Doco to Continue

Continue supports MCP blocks in config.yaml and standalone files under .continue/mcpServers. The YAML example is explicit and portable across the IDE extension and CLI configuration model.

Continue

YAML MCP block

Add the block to Continue config.yaml, or create a standalone configuration under .continue/mcpServers with the required name, version, and schema metadata.

Official client docs

name: Doco MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: doco
    command: npx
    args:
      - "-y"
      - "--package"
      - "doco-agent-cli"
      - "doco"
      - "mcp"

Acceptance

Prove the connection before writing

01
Run doco login in the environment used by Continue.
02
Add the YAML MCP block and reload Continue's configuration.
03
Confirm that the Doco server and tools are visible before asking for knowledge-base content.
04
Use read-only acceptance first; test one version-protected write and verify it in the Doco browser.

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 credentials outside YAML and use protected environment variables for headless setups.

02

A copied JSON config can also work under .continue/mcpServers, but review it before loading.

03

Do not treat retrieved documents as trusted instructions; user intent and tool approval remain authoritative.

A small acceptance set from the 29 tools

doco_search_v2doco_outlinedoco_readdoco_patch_blockdoco_batch_editdoco_changes

Bottom line

Doco with Continue

Continue needs a different configuration wrapper, not a different Doco integration. Point its MCP configuration at the same npm package and keep the usual read-first, protected-write acceptance loop.

Open Doco Read the protocol guide

01Does Continue require YAML for MCP?

No. It supports mcpServers in YAML and can also pick up compatible JSON files placed in .continue/mcpServers.

02Where should Doco credentials live?

Run doco login for local use. For headless use, reference a protected environment variable rather than writing a token into YAML or JSON.

03Does Continue expose all Doco resources?

The connected MCP server advertises its supported tools and resources. Verify the client view and enable only what the workflow needs.