Codex CLI

Before you start

You need Codex CLI and a SocialRouter account. No API key: Codex signs you in itself. Sign up at socialrouter.io if you have not yet. Codex connects straight to the hosted endpoint, so there is nothing to install.

Add the server

codex mcp add socialrouter --url https://mcp.socialrouter.io/mcp

This writes to ~/.codex/config.toml. Use .codex/config.toml at a repo root to scope it to one project instead; the block it writes is:

[mcp_servers.socialrouter]
url = "https://mcp.socialrouter.io/mcp"

That form holds no credential, so it is safe to commit. Each teammate signs in as themselves and is billed for what they run.

codex mcp login socialrouter

Codex opens your browser on the SocialRouter consent screen. Approve, and it keeps the token from then on. codex mcp logout socialrouter undoes it.

Using an API key instead

Use a key where a browser flow cannot run, such as CI or a container. Codex stores the name of an environment variable rather than the key itself:

export SOCIALROUTER_API_KEY=sr_live_your_key_here

codex mcp add socialrouter --url https://mcp.socialrouter.io/mcp --bearer-token-env-var SOCIALROUTER_API_KEY

[mcp_servers.socialrouter]
url = "https://mcp.socialrouter.io/mcp"
bearer_token_env_var = "SOCIALROUTER_API_KEY"

Create the key in the dashboard. It is shown once, at creation. Put the export line in your shell profile to make it stick. With a token configured, no sign-in ever runs.

Check it is connected

codex mcp list

socialrouter should be listed. Inside a session, /mcp shows the servers and the tools they add.

Ask for something

Get me Satya Nadella’s LinkedIn profile.

Codex finds the right service on its own. If you are not sure what to ask, try “What social media data can you pull with SocialRouter?”

If something goes wrong

The server fails to connect

Call the endpoint yourself to see the real answer:

curl -X POST https://mcp.socialrouter.io/mcp -H "Authorization: Bearer $SOCIALROUTER_API_KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

A 401 means the credential is wrong or revoked. If you are using a key, it can also mean SOCIALROUTER_API_KEY is not set in the shell you ran this from, which is the same shell Codex reads it from.

Putting the key in the file instead

If exporting a variable is awkward, send it as a static header in ~/.codex/config.toml, which lives outside your repos:

[mcp_servers.socialrouter]
url = "https://mcp.socialrouter.io/mcp"
http_headers = { Authorization = "Bearer sr_live_your_key_here" }

Never do this in a committed project config.

Next steps

Tools reference

What list_services, run, get_extraction and get_account do.

What you can pull

Every platform and service Codex can call.

Getting started

Clients

Reference

Before you start

If something goes wrong

Next steps

Tools reference

What you can pull

​Before you start

​If something goes wrong

​Next steps

Tools reference

What you can pull

Before you start

If something goes wrong

Next steps