How to Connect OpenAI Codex to LinkedIn
Short answer: Add the Cesar connector URL as a Streamable HTTP MCP server in the Codex CLI or the desktop app.
What you need
- Codex CLI, the Codex IDE extension, or the ChatGPT desktop app.
- A Cesar Pro or Business plan and the connector URL.
- Cesar open with the Chrome extension connected.
Before you add Codex
- Cesar is on the Pro or Business plan. In the app, open Integrations and enable LinkedIn MCP.
- Copy the connector URL. It already contains the token. Rotating the token in Integrations makes the previous URL stop working.
- Keep Cesar open in one browser tab with the Cesar extension installed and LinkedIn signed in. Green status means the bridge is up.
Step by step
1. Add it from the Codex CLI
Paste your connector URL into the command. Codex writes the entry to ~/.codex/config.toml.
codex mcp add cesar --url "https://mcp.cesar.chat/?token=<secret>"2. Or add it in the app
In the ChatGPT desktop app, open Settings → MCP servers. In the IDE extension, open the gear menu → MCP servers. Add a server named Cesar, choose Streamable HTTP, and paste the full connector URL. Restart if the tools do not show.
3. Check it
Run codex mcp list, or start Codex and type /mcp. You should see cesar. Then ask for get_connection_status.
Prompts to try first
- Use cesar to list inboxes.
- Find chats where I spoke last and nobody replied. Write a draft follow-up for each in replies.md. Do not send.
- Snooze the oldest one until Monday at 9:00 with set_chat_reminder.
Sending is not a tool. Replies land as drafts in Cesar. You send them yourself. The full list is on the LinkedIn MCP server page.
If it does not work
Codex asks for a login window
Cesar does not use a separate OAuth login for this server. The token is the ?token= on the URL. Paste that full URL as the server address.
Can this put my LinkedIn account at risk?
The agent cannot send a message. LinkedIn calls run one at a time, through the Cesar extension in your browser, not from a copy of the inbox on the server. Cesar does not run outreach sequences. Revoke the connector in Integrations and the URL stops working. Details are in Guardrails built in.