Connect Cursor to Cockpilot

Cursor, by Anysphere, 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 ~/.cursor/mcp.json.

Start free trial Sign in

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

Where the token comes from

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

Cursor, step by step

1. Open ~/.cursor/mcp.json, in your home folder (create it if needed): the global file, for every project.
2. Paste the block. If the file already has mcpServers, add only the cockpilot entry.

~/.cursor/mcp.json

{
  "mcpServers": {
    "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

To keep the token out of the file, Cursor resolves ${env:COCKPILOT_TOKEN} in headers. A project's .cursor/mcp.json works too, but with a token in it, keep it out of version control.

The file. ~/.cursor/mcp.json on macOS and Linux, %USERPROFILE%\.cursor\mcp.json on Windows.
Checked. On October 28, 2026, against the documentation at cursor.com.

Security

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

VS Code · Zed · Cline · Continue · All integrations · Version française

Start free trial Sign in