Connect Doco to your agent

Claude Code

In a terminal, an editor, or the Claude app's Code tab. Claude Code on the web uses your claude.ai connectors instead: add Doco there as a custom connector, with the URL https://doco.to/mcp. In the Claude desktop app, the Code tab already has Doco if you added it to Claude as a connector, so skip the desktop app's steps.

In a terminal

1

Add Doco for all your projects:

claude mcp add --transport http --scope user doco https://doco.to/mcp

2
Start Claude Code in your project. Run /mcp, pick collection and sign in. Doco opens in your browser: sign in and choose Allow.
```
/mcp
```
3
So Claude Code runs Doco's tools without asking you or, in auto mode, checking each call first, run /permissions and add this Allow rule to your user settings:
```
mcp__doco
```

In the Claude desktop app

1
Open Settings, then Developer, then Edit Config, and add Doco under mcpServers in claude_desktop_config.json (the whole file, if it's empty):
```
{
  "mcpServers": {
    "doco": { "type": "http", "url": "https://doco.to/mcp" }
  }
}
```
2
Open the Code tab and start a session in your project. Run /mcp, pick collection and sign in. Doco opens in your browser: sign in and choose Allow.
```
/mcp
```
3
So Claude Code runs Doco's tools without asking you or, in auto mode, checking each call first, run /permissions and add this Allow rule to your user settings:
```
mcp__doco
```

Stuck? Claude Code's own guide has the details.

Have Claude Code use Doco in every chat

Claude Code runs the Doco hook, which loads Doco's instructions at every session, so it needs no custom instructions.

Claude

Claude on the web, in its desktop app and on your phone, on any plan; a free plan holds one custom connector. On Team and Enterprise plans, an owner adds Doco once, then each member connects it.

On claude.ai

1
Go to Customize, then Connectors. Click + Add, then Add custom connector, name it Doco, enter this URL and click Add:
```
https://doco.to/mcp
```
2
Connect Doco when Claude asks. Doco opens in your browser: sign in and choose Allow.
3
In a chat, click + in the lower left, then Connectors, and make sure Doco is on. The first time Claude calls a Doco tool, choose Always allow.

Stuck? Claude's own guide has the details.

Have Claude use Doco in every chat

1

Click your initials in the lower left, then Settings, and paste this under Instructions for Claude:

I keep my team's shared memory in Doco (https://doco.to), connected here as Doco.

- At the start of each new chat, before anything else, ask me "Would you like to use Doco for this thread?" as a multiple-choice question: "Yes, <workspace>" for each workspace list_workspaces gives you, the recommended one first as "Yes, <workspace> (recommended)", then "No". Recommend the one this chat is most likely about. Don't ask if my message already names the workspace. If I say No, leave Doco out of the chat.
- Before answering anything about my work, call doco_brief with what I'm asking and the workspace I picked. Follow what it says I must obey, and mention the ids it gives you.
- When we settle on a decision, save it with doco_capture as a Decision: the question, the choice, and the options we dropped and why.
- Keep one Log of each chat in that workspace's Agents chats collection with doco_capture: one short line on what I asked and what came of it, not an account of everything you did.
- If Doco doesn't answer, tell me instead of guessing.

Codex

The Codex CLI, its editor extension and the ChatGPT desktop app share one setup, in ~/.codex/config.toml.

In a terminal

1
Add Doco and sign in. Doco opens in your browser: sign in and choose Allow.
```
codex mcp add doco --url https://doco.to/mcp
```
2
If Codex didn't open Doco, sign in with:
```
codex mcp login doco
```
3
The first time Codex asks before a Doco tool, choose Allow and don't ask me again.

In the ChatGPT desktop app or an editor

1

Add Doco to ~/.codex/config.toml:

[mcp_servers.doco]
url = "https://doco.to/mcp"

2
Start Codex in your project and sign in to Doco when it asks; in a terminal, this does the same. Doco opens in your browser: sign in and choose Allow.
```
codex mcp login doco
```
3
The first time Codex asks before a Doco tool, choose Allow and don't ask me again.

Stuck? Codex's own guide has the details.

Have Codex use Doco in every chat

Codex runs the Doco hook, which loads Doco's instructions at every session, so it needs no custom instructions.

ChatGPT

Only Business, Enterprise and Edu plans can add an MCP server that writes, and only on chatgpt.com: on Pro, ChatGPT can read Doco but not save to it, and Plus and Free can't add it. On Business, a workspace admin adds Doco and shares it; each member then installs it.

On chatgpt.com

1
Go to Plugins, click +, then Add custom MCP server. Name it Doco, enter this URL, choose OAuth to sign in, and click Create as a plugin:
```
https://doco.to/mcp
```
2
Go to Settings, then Plugins, pick Doco, click Install plugin, then Connect. Doco opens in your browser: sign in and choose Allow.
3
In a chat, type @ and pick Doco to be sure ChatGPT uses it.

Stuck? ChatGPT's own guide has the details.

Have ChatGPT use Doco in every chat

1

Go to Settings, then Personalization, turn on Enable customization, and paste this in Custom instructions:

I keep my team's shared memory in Doco (https://doco.to), connected here as Doco.

- At the start of each new chat, before anything else, ask me "Would you like to use Doco for this thread?" as a multiple-choice question: "Yes, <workspace>" for each workspace list_workspaces gives you, the recommended one first as "Yes, <workspace> (recommended)", then "No". Recommend the one this chat is most likely about. Don't ask if my message already names the workspace. If I say No, leave Doco out of the chat.
- Before answering anything about my work, call doco_brief with what I'm asking and the workspace I picked. Follow what it says I must obey, and mention the ids it gives you.
- When we settle on a decision, save it with doco_capture as a Decision: the question, the choice, and the options we dropped and why.
- Keep one Log of each chat in that workspace's Agents chats collection with doco_capture: one short line on what I asked and what came of it, not an account of everything you did.
- If Doco doesn't answer, tell me instead of guessing.

Gemini CLI

In a terminal

1
Add Doco for all your projects, trusted so Gemini CLI doesn't stop to ask on every call:
```
gemini mcp add --scope user --transport http --trust doco https://doco.to/mcp
```
2
Start Gemini CLI and sign in. Doco opens in your browser: sign in and choose Allow.
```
/mcp auth doco
```

In its settings file

1
Add Doco to ~/.gemini/settings.json, trusted so Gemini CLI doesn't stop to ask on every call (the whole file, if it's empty):
```
{
  "mcpServers": {
    "doco": { "httpUrl": "https://doco.to/mcp", "trust": true }
  }
}
```
2
Start Gemini CLI and sign in. Doco opens in your browser: sign in and choose Allow.
```
/mcp auth doco
```

Stuck? Gemini CLI's own guide has the details.

Have Gemini CLI use Doco in every chat

Gemini CLI runs the Doco hook, which loads Doco's instructions at every session, so it needs no custom instructions.

Gemini

Gemini lets only personal Google accounts add an MCP server like Doco: in the US, 18 or over, in English, with Keep Activity on. Work and school accounts can't yet; Gemini CLI takes any account.

On gemini.google.com

1
On a computer, open Settings, then Connected Apps (under Personal Intelligence, if you don't see it). Choose Add a custom app, enter this URL and click Next:
```
https://doco.to/mcp
```
2
Follow the steps on screen. Doco opens in your browser: sign in and choose Allow.
3
Doco now works in Gemini on the web and on your phone. Type @ and pick Doco to be sure Gemini uses it; Gemini asks you to confirm each time it saves to Doco.

Stuck? Gemini's own guide has the details.

Have Gemini use Doco in every chat

1

Open Menu, then Settings & help, then Personal Intelligence, then Instructions for Gemini. Tap Add +, paste this and tap Submit:

I keep my team's shared memory in Doco (https://doco.to), connected here as Doco.

- At the start of each new chat, before anything else, ask me "Would you like to use Doco for this thread?" as a multiple-choice question: "Yes, <workspace>" for each workspace list_workspaces gives you, the recommended one first as "Yes, <workspace> (recommended)", then "No". Recommend the one this chat is most likely about. Don't ask if my message already names the workspace. If I say No, leave Doco out of the chat.
- Before answering anything about my work, call doco_brief with what I'm asking and the workspace I picked. Follow what it says I must obey, and mention the ids it gives you.
- When we settle on a decision, save it with doco_capture as a Decision: the question, the choice, and the options we dropped and why.
- Keep one Log of each chat in that workspace's Agents chats collection with doco_capture: one short line on what I asked and what came of it, not an account of everything you did.
- If Doco doesn't answer, tell me instead of guessing.

Cursor

In the Cursor editor and the Cursor CLI.

In Cursor

1
Add Doco to ~/.cursor/mcp.json (the whole file, if it's empty), and restart Cursor:
```
{
  "mcpServers": {
    "doco": { "url": "https://doco.to/mcp" }
  }
}
```
2
Sign in to Doco when Cursor asks. Doco opens in your browser: sign in and choose Allow.
3
So Cursor runs Doco's tools without asking each time, add this to ~/.cursor/permissions.json:
```
{
  "mcpAllowlist": ["doco:*"]
}
```

Stuck? Cursor's own guide has the details.

Have Cursor use Doco in every chat

1

Open Customize, then Rules, and add this as a User Rule:

I keep my team's shared memory in Doco (https://doco.to), connected here as Doco.

- At the start of each new chat, before anything else, ask me "Would you like to use Doco for this thread?" as a multiple-choice question: "Yes, <workspace>" for each workspace list_workspaces gives you, the recommended one first as "Yes, <workspace> (recommended)", then "No". Recommend the one this chat is most likely about. Don't ask if my message already names the workspace. If I say No, leave Doco out of the chat.
- Before answering anything about my work, call doco_brief with what I'm asking and the workspace I picked. Follow what it says I must obey, and mention the ids it gives you.
- When we settle on a decision, save it with doco_capture as a Decision: the question, the choice, and the options we dropped and why.
- Keep one Log of each chat in that workspace's Agents chats collection with doco_capture: one short line on what I asked and what came of it, not an account of everything you did.
- If Doco doesn't answer, tell me instead of guessing.

Grok

On Grok Business and Enterprise, an admin adds Doco first at console.x.ai, under Grok Business, then Connectors.

On grok.com

1
Go to grok.com/connectors, click New Connector, then Custom, and enter this URL:
```
https://doco.to/mcp
```
2
Sign in when Grok asks. Doco opens in your browser: sign in and choose Allow.
3
Grok uses Doco by itself when a question touches it; mention Doco to be sure.

Stuck? Grok's own guide has the details.

Have Grok use Doco in every chat

1

Open Grok's settings, then Customize, and paste this in Custom Instructions:

I keep my team's shared memory in Doco (https://doco.to), connected here as Doco.

- At the start of each new chat, before anything else, ask me "Would you like to use Doco for this thread?" as a multiple-choice question: "Yes, <workspace>" for each workspace list_workspaces gives you, the recommended one first as "Yes, <workspace> (recommended)", then "No". Recommend the one this chat is most likely about. Don't ask if my message already names the workspace. If I say No, leave Doco out of the chat.
- Before answering anything about my work, call doco_brief with what I'm asking and the workspace I picked. Follow what it says I must obey, and mention the ids it gives you.
- When we settle on a decision, save it with doco_capture as a Decision: the question, the choice, and the options we dropped and why.
- Keep one Log of each chat in that workspace's Agents chats collection with doco_capture: one short line on what I asked and what came of it, not an account of everything you did.
- If Doco doesn't answer, tell me instead of guessing.

Qwen

Qwen Chat can't add Doco: it has no way to add an MCP server by its URL. Qwen Code, Qwen's agent in a terminal, can.

Qwen Code, in a terminal

1

Add Doco for all your projects:

qwen mcp add --scope user --transport http doco https://doco.to/mcp

2
Start Qwen Code, run /mcp and sign in. Doco opens in your browser: sign in and choose Allow.
```
/mcp
```

Stuck? Qwen's own guide has the details.

Have Qwen use Doco in every chat

1

Save this in ~/.qwen/QWEN.md, which Qwen Code reads in every project (at the end, if the file has something already):

I keep my team's shared memory in Doco (https://doco.to), connected here as Doco.

- At the start of each new chat, before anything else, ask me "Would you like to use Doco for this thread?" as a multiple-choice question: "Yes, <workspace>" for each workspace list_workspaces gives you, the recommended one first as "Yes, <workspace> (recommended)", then "No". Recommend the one this chat is most likely about. Don't ask if my message already names the workspace. If I say No, leave Doco out of the chat.
- Before answering anything about my work, call doco_brief with what I'm asking and the workspace I picked. Follow what it says I must obey, and mention the ids it gives you.
- When we settle on a decision, save it with doco_capture as a Decision: the question, the choice, and the options we dropped and why.
- Keep one Log of each chat in that workspace's Agents chats collection with doco_capture: one short line on what I asked and what came of it, not an account of everything you did.
- If Doco doesn't answer, tell me instead of guessing.