OpenAI Codex

The OpenAI Codex CLI connects to Social media studio’s remote Streamable HTTP MCP server using its url and an X-API-Key header.

You need an API key (format sk_live_...) to connect. Generate one from Settings > API Access, or see Authentication.

Setup

Run the CLI command

codex mcp add --transport http so-me-studio \
  https://api.so-me.studio/mcp \
  -H "X-API-Key: sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"

Verify the connection

Run /mcp in a Codex session to see so-me-studio listed with its tools.

Alternative: config.toml

Edit ~/.codex/config.toml directly (or .codex/config.toml in a trusted project):

config.toml

[mcp_servers.so-me-studio]
url = "https://api.so-me.studio/mcp"

[mcp_servers.so-me-studio.env_http_headers]
X-API-Key = "SO_ME_API_KEY"

With env_http_headers, the value is the name of an environment variable, not the key itself. Export SO_ME_API_KEY with your actual sk_live_... key in your shell so Codex can read it at startup.

To send the header value inline instead (no environment variable), use http_headers:

config.toml

[mcp_servers.so-me-studio]
url = "https://api.so-me.studio/mcp"

[mcp_servers.so-me-studio.http_headers]
X-API-Key = "sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"

Scopes

Scope	File Location
Global	`~/.codex/config.toml`
Project	`.codex/config.toml` (trusted projects only)

Troubleshooting

Missing X-API-Key / 401

If you used env_http_headers, confirm the referenced environment variable is exported in the same shell that launches Codex and contains an active sk_live_... key.

405 Method Not Allowed

The Social media studio server runs in stateless Streamable HTTP mode (POST only). Keep the transport set to http — do not configure an SSE endpoint.

MCP Server

Other Agents

Setup

Alternative: config.toml

Scopes

Troubleshooting

​Setup

​Alternative: config.toml

​Scopes

​Troubleshooting

Setup

Alternative: config.toml

Scopes

Troubleshooting