Connect Zed to Cockpilot

Zed, by Zed Industries, 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 ~/.config/zed/settings.json.

Start free trial Sign in

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

Where the token comes from

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

Zed, step by step

1. In the Command Palette, run zed: open settings file.
2. Paste the block. If the file already has context_servers, add only the cockpilot entry.
3. In Settings, AI, MCP Servers, the dot next to Cockpilot turns green: Server is active.

~/.config/zed/settings.json

{
  "context_servers": {
    "cockpilot": {
      "url": "https://your-team.cockpilot.si/mcp",
      "headers": {
        "Authorization": "Bearer ck_..."
      }
    }
  }
}

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

Good to know

Without an Authorization header, Zed would run the server's OAuth flow instead.

The file. ~/.config/zed/settings.json on macOS and Linux.
Checked. On October 28, 2026, against the documentation at zed.dev.

Security

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

Cline · Continue · Devin Desktop · Cursor · All integrations · Version française

Start free trial Sign in