Setup guide · MCP

Set up seenpaid in Codex

Codex is OpenAI’s coding agent. Codex writes and runs code; it has no access to your social accounts. Add seenpaid as a Streamable HTTP server in its config and it can announce what it just built, on the schedule you give it.

Start your 7-day trial →Jump to the setup

Card required, no charge until day 8. MCP access is on every plan.

$
Endpoint
api.seenpaid.com/mcp
Transport
Streamable HTTP
Auth
Bearer sp_…
Tools
50

Four steps

How to connect Codex to seenpaid

You need a seenpaid API key and one paste.

  1. 1

    Create an API key

    In seenpaid, open Settings → API keys and create a key. It starts with sp_ and is shown once, so copy it straight into the next step. You can revoke it at any time.

    Open Settings → API keys
  2. 2

    Add seenpaid to Codex

    Add this table to ~/.codex/config.toml, then export the key in your shell: export SEENPAID_API_KEY=sp_your_api_key. Codex reads the variable and sends it as the Bearer token, so the key never sits in the config file.

    ~/.codex/config.toml
    [mcp_servers.seenpaid]
url = "https://api.seenpaid.com/mcp"
bearer_token_env_var = "SEENPAID_API_KEY"

    Replace sp_your_api_key with your key.

    Checked against the official docs: learn.chatgpt.com/docs/extend/mcp?surface=cli (developers.openai.com/codex/mcp redirects there) — [mcp_servers.<name>] with url and bearer_token_env_var.

  3. 3

    Restart and verify

    Run codex mcp list to see seenpaid configured, then type /mcp inside the Codex TUI to see it active with its tools.

  4. 4

    Ask for your first post

    Start with “Which of my social accounts are connected?” — Codex calls list_accounts and names your channels. If none are connected yet, ask for a connect link: that one step needs you in a browser.

Try asking

First things to ask Codex

Plain requests. Under each one, the seenpaid tools Codex calls to answer it.

  • Which of my social accounts are connected?

    Callslist_accounts

  • Write a post about the fix you just made and schedule it to X and Bluesky for 9am tomorrow.

    Callsschedule_post

  • Check this caption against every platform’s limits before we post it.

    Callsget_platform_requirementsvalidate_post

  • Which posts got clicks but no sales?

    Callsget_dead_posts needs revenue tracking

Revenue tracking is optional and off by default. Scheduling works without it. Every tool →

Troubleshooting

If it does not connect

401 Unauthorized

The request reached seenpaid but no valid credential came with it. Check the key starts with sp_, was not revoked, and is sent as “Authorization: Bearer sp_…” with the word Bearer and one space. seenpaid also answers 401 when the workspace has no active trial or plan, even with a correct key.

Wrong URL, or the server never connects

The endpoint is exactly https://api.seenpaid.com/mcp — not seenpaid.com, and not an /sse URL. seenpaid speaks Streamable HTTP only; a client set to SSE will not connect. Opening the URL in a browser shows a short explainer page, which is expected.

OAuth or API key — which one?

Config files and command-line clients send the sp_ key as a header. Connector screens in apps (claude.ai, Claude Desktop, ChatGPT, Grok) have no key field: they sign in to seenpaid with OAuth instead. Never paste your key into an OAuth client ID or secret field.

Codex connects but every call is unauthorized

The variable is read from the environment Codex was started in. Export SEENPAID_API_KEY in the same shell (or your shell profile) and restart Codex.

FAQ

Codex and seenpaid, answered

Not on its own — it has no credentials for your accounts. Connected to seenpaid’s MCP server it can schedule and publish to the 21 platforms seenpaid supports, and report back per platform what went out.

Create an API key in seenpaid under Settings → API keys, then add https://api.seenpaid.com/mcp as a remote MCP server with the key sent as an Authorization: Bearer header. Add this table to ~/.codex/config.toml, then export the key in your shell: export SEENPAID_API_KEY=sp_your_api_key. Codex reads the variable and sends it as the Bearer token, so the key never sits in the config file.

Use all 50 seenpaid tools: schedule, edit and cancel posts, check each platform’s limits before publishing, generate images and carousels, and read what published. Revenue tools (which post made money) work only if you switch on revenue tracking, which is optional and off by default.

No. MCP access is included on every seenpaid plan and in the 7-day trial.

It acts through a key or sign-in scoped to one seenpaid workspace; an API key can be revoked in Settings at any time. No tool returns your social passwords or platform tokens, and it cannot connect a new account on its own: it hands you a link and you sign in.

Also works with

Every other setup guide

Same server, same tools. Pick your client for its exact setup.

How the agent works MCP server reference