Connect n8n to Cockpilot
n8n 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 a few fields to fill in.
What n8n 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. n8n sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the n8n row: it creates your token, n8n-<you>.
- ck_ followed by 43 characters. Copy it right away: it is shown only once.
- n8n asks for it. Paste it when it does: see the steps.
n8n, step by step
- 1. In a workflow with an AI Agent, add the MCP Client Tool node.
- 2. Endpoint: the address. Server Transport: HTTP Streamable.
- 3. Authentication: Bearer Auth, then a new credential with the token as Bearer Token.
- 4. Tools to Include: All, or Selected to keep only what the agent needs.
The address
https://your-team.cockpilot.si/mcpPut in your space's address (your-team).
Good to know
The docs page still shows the first version of the node (SSE Endpoint); Endpoint, Server Transport (HTTP Streamable by default since version 1.2) and Bearer Auth come from the node's source, packages/@n8n/nodes-langchain/nodes/mcp/McpClientTool in the n8n repository.
- Checked. On October 28, 2026, against the documentation at docs.n8n.io.
Security
- One token per client. n8n 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 · OpenClaw · Claude · ChatGPT · All integrations · Version française