Connect Gemini CLI to Cockpilot
Gemini CLI, by Google, 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 command in a terminal.
What Gemini CLI 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. Gemini CLI sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the Gemini CLI row: it creates your token, gemini-cli-<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.
Gemini CLI, step by step
- 1. Paste the command in a terminal: --scope user writes Cockpilot to ~/.gemini/settings.json, for every project.
- 2. Start Gemini CLI: Cockpilot's tools are there.
Terminal
gemini mcp add --transport http --scope user --header "Authorization: Bearer ck_..." cockpilot https://your-team.cockpilot.si/mcpPut in your space's address (your-team) and your token (ck_...).
Good to know
Since June 18, 2026, Gemini CLI serves paid Gemini API keys and enterprise licences only; free and Google AI Pro or Ultra users moved to Antigravity CLI. In settings.json the server uses httpUrl, and string values can reference $COCKPILOT_TOKEN.
- The file. ~/.gemini/settings.json on macOS and Linux, %USERPROFILE%\.gemini\settings.json on Windows.
- Checked. On October 28, 2026, against the documentation at geminicli.com.
Security
- One token per client. Gemini CLI 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
Claude Code · Codex · Cursor · VS Code · All integrations · Version française