Connect Codex to Cockpilot
Codex, by OpenAI, 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 Codex 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. Codex sees and changes what you can, nothing else.
Where the token comes from
- In Cockpilot, open Connections. Then the Codex row: it creates your token, codex-<you>.
- ck_ followed by 43 characters. Copy it right away: it is shown only once.
- It goes in COCKPILOT_TOKEN. In the environment Codex starts from: setx on Windows, then a new terminal; on macOS or Linux, the export line in your shell profile.
Windows
setx COCKPILOT_TOKEN "ck_..."
macOS, Linux
export COCKPILOT_TOKEN="ck_..."
Codex, step by step
- 1. Put the token in COCKPILOT_TOKEN, then open a new terminal.
- 2. Paste the command: it writes the server to ~/.codex/config.toml, shared by the CLI, the IDE extension and the app.
- 3. Check with codex mcp list.
Terminal
codex mcp add cockpilot --url https://your-team.cockpilot.si/mcp --bearer-token-env-var COCKPILOT_TOKENPut in your space's address (your-team).
Good to know
The same server in config.toml: [mcp_servers.cockpilot] with url and bearer_token_env_var = "COCKPILOT_TOKEN". The --bearer-token-env-var flag is in the Codex CLI source (codex-rs/cli/src/mcp_cmd.rs).
- The file. ~/.codex/config.toml on macOS and Linux, %USERPROFILE%\.codex\config.toml on Windows.
- Checked. On October 28, 2026, against the documentation at learn.chatgpt.com.
Security
- One token per client. Codex 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
Gemini CLI · Claude Code · Cursor · VS Code · All integrations · Version française