Connect VS Code to Cockpilot
VS Code, by Microsoft, 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.
What VS Code 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. VS Code sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the VS Code row: it creates your token, vscode-<you>.
- ck_ followed by 43 characters. Copy it right away: it is shown only once.
- VS Code asks for it. Paste it when it does: see the steps.
VS Code, step by step
- 1. In the Command Palette, run MCP: Open User Configuration: it opens the mcp.json of your profile.
- 2. Paste the block. If the file already has servers, add the cockpilot entry and the input.
- 3. When the server first starts, VS Code asks for the token: paste it. Cockpilot's tools are then in Copilot Chat, agent mode.
Configuration
{
"inputs": [
{
"type": "promptString",
"id": "cockpilot-token",
"description": "Cockpilot token",
"password": true
}
],
"servers": {
"cockpilot": {
"type": "http",
"url": "https://your-team.cockpilot.si/mcp",
"headers": {
"Authorization": "Bearer ${input:cockpilot-token}"
}
}
}
}Put in your space's address (your-team).Good to know
A workspace's .vscode/mcp.json takes the same block. The input keeps the token out of the file; ${env:COCKPILOT_TOKEN} also works in header values.
- Checked. On October 28, 2026, against the documentation at code.visualstudio.com.
Security
- One token per client. VS Code 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
Zed · Cline · Continue · Devin Desktop · All integrations · Version française