# Schedule social media posts from Codex

> Add Fuxux to OpenAI Codex as a remote MCP server and schedule posts to 14 social platforms from the terminal, by signing in or with an API key.

Canonical: https://www.fuxux.com/codex

Remote MCP server

Codex can write the release notes. Add Fuxux as a remote MCP server and it can also turn them into posts, save them as drafts or schedule them to 14 platforms, from the same session.

[MCP docs](https://www.fuxux.com/mcp/docs)

## Sign in (no key)

Uses Codex's own MCP login. Works on every Fuxux plan, including Free.

1. **Add the server** Run this in your terminal. It writes the server to ~/.codex/config.toml.
   ```
   codex mcp add fuxux --url https://www.fuxux.com/api/mcp
   ```
2. **Log in** Your browser opens Fuxux: sign in and choose Allow access.
   ```
   codex mcp login fuxux
   ```
3. **Check it** Run codex mcp list, or /mcp inside Codex, then ask "list my connected accounts in Fuxux". Connect your social accounts in Fuxux first.
   ```
   codex mcp list
   ```

## Or use an API key

For machines without a browser, or if you prefer a key.

1. **Put your key in an environment variable** Create a key on the API keys page in Fuxux.
   ```
   FUXUX_API_KEY=fx_live_your_key_here
   ```
2. **Add the server to config.toml** Codex reads the key from the variable you name and sends it as a bearer token, so the key is not stored in the file.
   ```
   [mcp_servers.fuxux]
   url = "https://www.fuxux.com/api/mcp"
   bearer_token_env_var = "FUXUX_API_KEY"
   ```

## Codex writes the release notes, Fuxux posts them

Codex talks to Fuxux as a remote MCP server. The command codex mcp add fuxux, with the --url flag, records the server in ~/.codex/config.toml, and codex mcp login fuxux runs Codex's own MCP login: Fuxux opens in your browser, you approve access, and you are done. Signing in this way needs no paid Fuxux plan.

Codex sessions tend to end with something worth announcing. If Codex has just drafted release notes in the repository, ask it to reuse that text for each network you post to, keeping every caption inside its limit (280 characters on X, 500 on Threads). When it schedules, Fuxux needs a time with a time zone, so let Codex convert your local time before it sends the post.

If the login does not complete on your machine, switch to a key. Export it as FUXUX_API_KEY, then name that variable in config.toml with bearer_token_env_var; Codex then sends the key as a bearer token, and the file only holds the variable's name. Run codex mcp list, or /mcp inside Codex, to confirm the server is there.

## Things to ask Codex

- “You just wrote the release notes for this version. Turn them into a Threads post and a LinkedIn post and schedule both for 9:00 tomorrow, Berlin time.”
- “Look at the pull requests merged for this release and draft one Telegram message for our users' channel. Keep it as a draft.”
- “Which posts are scheduled in Fuxux for next month? Give me the dates and platforms.”
- “Delete the draft in Fuxux about the old beta; we are not shipping it.”

## Codex FAQ

### Does Codex work on the Fuxux Free plan?

Yes, through codex mcp login fuxux: you sign in to Fuxux in your browser and no key is stored, so no paid plan is needed. Free covers 3 connected accounts and 5 published posts a month; posting to X needs a paid plan.

### When does Codex need an API key?

Only if codex mcp login does not complete on your machine. A key needs a Creator, Growth or Pro plan, at no extra cost, starts with fx_live_ and is shown once; Codex reads it from the variable named in bearer_token_env_var, and it works until you revoke it.

### Which tools does Codex get?

Nine: whoami, list connected accounts, dashboard, analytics, and list, get, create, update and delete posts. Creating a post can publish it now, schedule it, or save it as a draft.

### Can Codex post without asking me?

It can publish, because publishing is one of the tools. If you want to approve everything first, tell it to "always save posts as drafts", then review and schedule them in your Fuxux calendar.

### How do I remove Codex's access?

Remove the Codex connection under Settings, then Connected apps in Fuxux, or revoke its key on the API keys page; either stops it straight away. You can then delete the [mcp_servers.fuxux] entry from ~/.codex/config.toml.

### Is this an official OpenAI integration?

No. Fuxux isn't affiliated with OpenAI. This uses the remote MCP server setting that Codex offers every user.

## Other assistants

- [ClaudeConnector directory](https://www.fuxux.com/claude)
- [Claude CodeOne command](https://www.fuxux.com/claude-code)
- [ChatGPTPlugin directory](https://www.fuxux.com/chatgpt)
- [Gemini CLIExtension](https://www.fuxux.com/gemini)
- [CursorOne-click install](https://www.fuxux.com/cursor)
- [PerplexityCustom connector](https://www.fuxux.com/perplexity)
- [Grok BuildRemote MCP server](https://www.fuxux.com/grok-build)
- [Hermes AgentRemote MCP server](https://www.fuxux.com/hermes)
- [Kimi CodeRemote MCP server](https://www.fuxux.com/kimi)
- [OpenClawSkill on ClawHub](https://www.fuxux.com/openclaw)
- [Cue & ManusCustom connector](https://www.fuxux.com/cue)

Related: [MCP integration](https://www.fuxux.com/mcp) · [AI agents](https://www.fuxux.com/agents) · [Pricing](https://www.fuxux.com/pricing) · [AI schedulers compared](https://www.fuxux.com/blog/social-media-schedulers-for-chatgpt-and-claude)
