Connect Claude Code to Cockpilot
Claude Code, by Anthropic, 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 command in a terminal.
What Claude Code 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. Claude Code sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the Claude Code row: it creates your token, claude-code-<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.
Claude Code, step by step
- 1. Paste the command in a terminal: --scope user makes Cockpilot available in every project.
- 2. In a Claude Code session, /mcp shows Cockpilot and its tools.
Terminal
claude mcp add --transport http --scope user cockpilot https://your-team.cockpilot.si/mcp --header "Authorization: Bearer ck_..."Put in your space's address (your-team) and your token (ck_...).
Good to know
The command writes the token to ~/.claude.json. To keep it out, set COCKPILOT_TOKEN in your environment and use claude mcp add-json with "Authorization": "Bearer ${COCKPILOT_TOKEN}": Claude Code expands variables in headers.
- The file. ~/.claude.json on macOS and Linux, %USERPROFILE%\.claude.json on Windows.
- Checked. On October 28, 2026, against the documentation at code.claude.com.
Security
- One token per client. Claude Code 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
Codex · Gemini CLI · Cursor · VS Code · All integrations · Version française