Connect Devin Desktop to Cockpilot
Devin Desktop, by Cognition, works on your team's tasks, projects, contacts and KPIs through Cockpilot's 40 MCP tools, with your rights and never more. A personal token, then one block in ~/.config/devin/mcp_config.json.
What Devin Desktop gets
- 40 MCP tools. 14 that read and 26 that write, from the day's briefing to the month's KPIs.
- Your team's work. Its tasks, projects, contacts and KPIs.
- Your rights, never more. Devin Desktop sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the Devin Desktop row: it creates your token, devin-<you>.
- ck_ followed by 43 characters. Copy it right away: it is shown only once.
- It goes in the block. As a Bearer token in the Authorization header: see the steps.
Devin Desktop, step by step
- 1. Open ~/.config/devin/mcp_config.json (on Windows, %APPDATA%\devin\mcp_config.json): the global file of Devin CLI, which the Devin Local agent reads.
- 2. Paste the block. If the file already has mcpServers, add only the cockpilot entry.
~/.config/devin/mcp_config.json
{
"mcpServers": {
"cockpilot": {
"url": "https://your-team.cockpilot.si/mcp",
"transport": "http",
"headers": {
"Authorization": "Bearer ck_..."
}
}
}
}Put in your space's address (your-team) and your token (ck_...).Good to know
Formerly Windsurf: docs.windsurf.com now redirects to Devin Desktop's docs. The default agent of new tabs, Devin Local, reads Devin CLI's MCP configuration; the legacy Cascade agent's own page is https://docs.devin.ai/desktop/cascade/mcp.
- The file. ~/.config/devin/mcp_config.json on macOS and Linux, %APPDATA%\devin\mcp_config.json on Windows.
- Checked. On October 28, 2026, against the documentation at docs.devin.ai.
Security
- One token per client. Devin Desktop has its own: revoke it from the Security page.
- Deletions go to the trash. They can be restored for thirty days, and every change is in the journal.
Other clients
Cursor · VS Code · Zed · Cline · All integrations · Version française