Connect Cline to Cockpilot

Cline 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 its configuration.

Start free trial Sign in

What Cline 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. Cline sees and changes what you can, nothing else.

Where the token comes from

In Cockpilot, open Connections. Then the Cline row: it creates your token, cline-<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.

Cline, step by step

1. In Cline, open MCP Servers, Configure, then Configure MCP Servers: it opens cline_mcp_settings.json.
2. Add the cockpilot entry under mcpServers. Keep type streamableHttp: without it, Cline falls back to the old SSE transport.

Configuration

{
  "mcpServers": {
    "cockpilot": {
      "type": "streamableHttp",
      "url": "https://your-team.cockpilot.si/mcp",
      "headers": {
        "Authorization": "Bearer ck_..."
      },
      "disabled": false
    }
  }
}

Put in your space's address (your-team) and your token (ck_...).

Good to know

Cline CLI: cline mcp add cockpilot https://your-team.cockpilot.si/mcp --transport http --header "Authorization: Bearer ck_..." --yes, written to ~/.cline/data/settings/cline_mcp_settings.json.

Checked. On October 28, 2026, against the documentation at docs.cline.bot.

Security

One token per client. Cline 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

Continue · Devin Desktop · Cursor · VS Code · All integrations · Version française

Start free trial Sign in