Codex CLI is built for heads-down work: it lives in your terminal, reads your project, and gets things done with minimal ceremony. Social media is about as far from that mode as software gets — which is exactly why announcements written 'later, in the other tool' so often never happen.
Nimply brings the two together through MCP. Registered in Codex's config.toml, the Nimply server gives your sessions tools for creating and managing posts, browsing channels, and pulling analytics across Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Pinterest, and Threads. "Use nimply to draft a post about this repo's new release and save it as a draft" becomes something Codex just does.
What is Codex CLI, and why the bridge?
Codex CLI is OpenAI's open-source coding agent for the terminal. It configures MCP servers declaratively in ~/.codex/config.toml, historically expecting local command-based servers. Nimply's server is remote HTTP with an auth header — so the most reliable connection runs through mcp-remote, the standard bridge that launches via npx and forwards Codex's MCP traffic to the remote endpoint, header included.
Recent Codex versions also support remote servers natively with a url field, in which case the bridge is unnecessary. Either way, authentication is a Nimply API key created under Settings → Developers: it is scoped to one workspace and a permission set you choose, and revoking it in Nimply cuts the agent off instantly.
What Codex CLI can do with Nimply
Announce the release you just cut
Codex has the full context of what changed — it may have written half of it. Asking it to draft a release post from the repo produces copy grounded in the actual work, saved as a draft in Nimply for you to polish and schedule.
Build posting into your automation
Because Codex runs headlessly as well as interactively, a Nimply-connected session can be part of a scripted routine: summarize what shipped, draft the announcement, save it as a draft for human review. Content creation becomes a repeatable step instead of an afterthought.
Manage the queue without a browser
List what is scheduled, inspect a draft, fix a caption, move a post to a better slot — the full lifecycle of your content queue is available as terminal conversation, using the same session you are coding in.
Pull performance numbers into your terminal
Nimply's analytics tools work from Codex too. Ask how recent posts performed or how a channel is trending, and use the answer to decide what the next announcement should look like — all without switching windows.
Connect Codex CLI to Nimply
Setup is an API key and a config.toml entry. The mcp-remote bridge needs Node 18 or newer.
- 1
Create an API key
In Nimply, open Settings → Developers and create a key with the scopes your agent should have. Keys begin with nim_live_ and are revocable on their own, so dedicate one to Codex.
- 2
Add the mcp-remote bridge to config.toml
Register Nimply in ~/.codex/config.toml using the standard mcp-remote bridge, which attaches the remote server with your auth header:
~/.codex/config.toml[mcp_servers.nimply] command = "npx" args = [ "-y", "mcp-remote", "https://mcp.nimply.io/mcp", "--header", "Authorization: Bearer nim_live_YOUR_KEY" ] - 3
Or use native remote support
If your Codex version supports remote MCP servers directly (a url field), you can skip the bridge entirely:
~/.codex/config.toml[mcp_servers.nimply] url = "https://mcp.nimply.io/mcp" http_headers = { "Authorization" = "Bearer nim_live_YOUR_KEY" } - 4
Restart and verify
Restart Codex; the Nimply tools appear in the session's tool list. Check server status with codex mcp list (or your version's equivalent), then try asking Codex to list your connected channels.
Frequently asked questions
Why does Codex CLI need the mcp-remote bridge?
Codex configures MCP servers in config.toml and traditionally launches them as local commands. mcp-remote is a small bridge that starts locally via npx and relays traffic to a remote HTTP server, passing your Authorization header along — the most reliable way to attach Nimply across Codex versions. Newer versions with native url support do not need it.
Can I connect Codex CLI with OAuth instead of a key?
No — the OAuth click-and-approve flow is for connector-style clients like claude.ai, ChatGPT, and Claude Desktop. File-configured tools like Codex authenticate with an API key from Settings → Developers.
The bridge fails to start. What should I check?
npx mcp-remote requires Node 18 or newer. Run the npx command from your config manually in a terminal to see the actual error — version issues and typos in the header are the usual causes.
Is it safe to keep the API key in config.toml?
Treat the key like a password: config.toml lives in your home directory, so keep it out of shared machines and never commit it anywhere. Use a dedicated key for Codex so you can revoke it from Settings → Developers without disturbing other integrations.
Which social networks can Codex post to?
Every channel connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads.
Codex starts, but the Nimply tools are not listed. Why?
Check the server status with codex mcp list (or the equivalent in your version). If the server shows an error, verify the URL and the Authorization header value — a mistyped or revoked key produces auth failures.
Works well alongside
Ready to try it?
Create a free Nimply account, connect your channels, and you're one config entry away.