Connect Continue to Cockpilot

Continue 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 ~/.continue/config.yaml.

Start free trial Sign in

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

Where the token comes from

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

Continue, step by step

1. Open ~/.continue/config.yaml, your user configuration.
2. Add the Cockpilot entry under mcpServers.
3. Cockpilot's tools work in agent mode only.

~/.continue/config.yaml

mcpServers:
  - name: Cockpilot
    type: streamable-http
    url: https://your-team.cockpilot.si/mcp
    requestOptions:
      headers:
        Authorization: Bearer ck_...

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

Good to know

requestOptions on an sse or streamable-http server takes the same format as a model's, headers included (docs.continue.dev/reference, mcpServers). A standalone file in .continue/mcpServers/ also needs name, version and schema at the top.

The file. ~/.continue/config.yaml on macOS and Linux, %USERPROFILE%\.continue\config.yaml on Windows.
Checked. On October 28, 2026, against the documentation at docs.continue.dev.

Security

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

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

Start free trial Sign in