MCP integration · Gemini CLI

Doco × Gemini CLI

Connect Google Gemini CLI to Doco through a local MCP server. Use 29 tools to search and read documents, cite stable block IDs, and request version-protected writes while teammates collaborate in real time.

Copy the setup Official client docs

Configuration

Connect Doco to Gemini CLI

Run doco login in the environment that launches Gemini CLI. Keep trust: false so tool-call confirmations stay on while you verify the connection and first write.

Gemini CLI

User or project settings.json

Merge this mcpServers entry into ~/.gemini/settings.json, or project .gemini/settings.json. Keep existing settings and leave trust: false.

Official client docs

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

Acceptance

Prove the connection before writing

01
Run doco login and confirm the intended Doco workspace and scopes.
02
Add the JSON entry, restart Gemini CLI, and check /mcp for the doco server and tools.
03
Ask Gemini CLI to search a document and cite a stable block ID from a read-only result.
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

Keep trust: false to retain tool-call confirmations; review each proposed write before approving it.

02

Keep login credentials outside settings.json 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 Gemini CLI

Gemini CLI connects through its existing mcpServers settings. Keep confirmations on, verify the read path first, and use Doco version checks for edits to shared documents.

Open Doco Read the protocol guide

01Why does the example set trust to false?

It keeps tool-call confirmations on instead of automatically trusting the Doco server. You can review the requested operation before it runs.

02Which Gemini CLI settings file should I use?

Use ~/.gemini/settings.json for your user setup, or .gemini/settings.json for a reviewed project configuration. Merge the entry without replacing unrelated settings.

03Do I need a Doco token in the JSON?

No. Run doco login locally in the same environment as Gemini CLI. Do not put credentials in shared project settings.