Connect OpenClaw to Cockpilot
OpenClaw 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 ~/.openclaw/openclaw.json.
What OpenClaw 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. OpenClaw sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the OpenClaw row: it creates your token, openclaw-<you>.
- ck_ followed by 43 characters. Copy it right away: it is shown only once.
- It goes in COCKPILOT_TOKEN. In OpenClaw's environment.
Environment
COCKPILOT_TOKEN=ck_...
OpenClaw, step by step
- 1. Create OpenClaw's token, then add the mcp block to ~/.openclaw/openclaw.json, with COCKPILOT_TOKEN in its environment.
- 2. Install the Cockpilot skill: https://cockpilot.si/openclaw/SKILL.md in ~/.openclaw/skills/cockpilot/.
- 3. Let Cockpilot alert OpenClaw: the gateway's hooks, and an openclaw webhook on the task events.
~/.openclaw/openclaw.json
mcp: {
servers: {
cockpilot: {
url: "https://your-team.cockpilot.si/mcp",
transport: "streamable-http",
headers: { Authorization: "Bearer ${COCKPILOT_TOKEN}" },
},
},
},Put in your space's address (your-team).Good to know
Without transport: "streamable-http", OpenClaw uses SSE. The hooks format: https://docs.openclaw.ai/gateway/config-hooks. Full guide: https://cockpilot.si/integrations/#openclaw.
- The file. ~/.openclaw/openclaw.json on macOS and Linux, %USERPROFILE%\.openclaw\openclaw.json on Windows.
- Checked. On October 28, 2026, against the documentation at docs.openclaw.ai.
Security
- One token per client. OpenClaw 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
Hermes · Claude Code · Codex · Gemini CLI · All integrations · Version française