← All articles

Codex MCP Setup for Social Posting: Announce Releases From Codex

OpenAI Codex can read your repository, write the release notes and open the pull request. With one MCP server added to its config, it can also announce the release on X, LinkedIn, Bluesky, Threads and the rest of your social accounts, in the same session.

This guide shows how to connect 1Social to Codex through MCP. It covers the config.toml entry, the OAuth login, prompts that turn a changelog into posts, and the limits worth knowing before you let an agent post in your name.

Codex and MCP in one paragraph

Codex supports MCP servers over stdio and streamable HTTP. Servers live in ~/.codex/config.toml, or in .codex/config.toml inside a trusted project. The same configuration is shared by the Codex CLI, the Codex IDE extension and the ChatGPT desktop app, so you set up a server once and use it everywhere. Inside a session, /mcp lists the servers Codex has loaded.

1Social is a remote MCP server for social publishing. It handles each network's API and gives Codex a few tools: list your connected accounts, preview a post against every network's rules, publish or schedule it, attach media, retry one failed network, and return a receipt per network.

Step 1: Set up 1Social

  1. Create an account at 1social.dev/login. Every plan starts with a free trial.
  2. Connect the networks you want to post to: Instagram, TikTok, LinkedIn, X, Bluesky, Threads, Facebook Pages or YouTube Shorts. Each signs in through its own page in your browser.
  3. Choose a plan on the pricing page. Solo is $29 a month for 600 deliveries. Pro is $49 a month for 1,600 deliveries, up to five accounts per network, and scheduling up to 30 days ahead.

Step 2: Add 1Social to config.toml

Open ~/.codex/config.toml and add:

[mcp_servers.1social]
url = "https://mcp.1social.dev/mcp"

A url entry tells Codex this is a streamable HTTP server. OAuth is the default sign-in for HTTP servers, so there is no token to paste.

If you prefer the desktop app, its MCP servers settings write to the same file.

Step 3: Sign in

Run the login separately:

codex mcp login 1social

Codex opens the 1Social sign-in. Approve it, return to the terminal, and the server is ready. Start a Codex session and type /mcp to confirm that 1social is listed.

If you already use 1Social in ChatGPT through its plugin listing, "Instagram & TikTok by 1Social", that listing works in Codex too. The config entry above is the direct route for the CLI and IDE.

Step 4: Announce a release

A prompt that works well right after a merge:

Read the diff of the last release tag and CHANGELOG.md.
Write release posts for X (under 280 characters), LinkedIn and Threads (under 500).
Preview them with 1Social and show me any network that would reject them.
Do not publish until I confirm.

Codex drafts, runs the 1Social preview, and shows what each network would accept. Then:

Publish X and Threads now. Schedule LinkedIn for Tuesday at 9:00 my time.

The result comes back as one line per network: published, failed with a reason, or unconfirmed when the network does not report back.

More prompts

A changelog digest every Friday:

Summarize this week's merged PRs into one LinkedIn post and one X post.
Skip internal refactors. Preview, then wait for my OK.

Post a screenshot:

Attach docs/images/new-editor.png and post it to X and Bluesky
with a one-sentence caption about the new editor.

Recover from a failure:

The Bluesky post failed. Check the reason in 1Social, shorten it if needed,
and retry only Bluesky.

See the queue:

What is scheduled in 1Social for the next 7 days?

Controlling what Codex can do

Codex lets you tune each MCP server in config.toml. Two settings are useful for a publishing tool:

  • enabled_tools and disabled_tools let you limit which 1Social tools Codex may call. For example, you can give a project read and preview tools only.
  • tool_timeout_sec sets how long Codex waits for a tool. The default of 60 seconds is fine for text posts. Video uploads may need more.

Approval prompts are your friend here. A post to a public account is the kind of action you want to confirm by hand.

Why post from a coding agent at all

Release announcements are the first thing to slip when a team is busy. Not because they are hard, but because they need a context switch: open each app, rewrite the update to fit, upload the screenshot again. Codex already has the context. It knows what changed, which issue it closes and what the screenshot shows. Letting the same agent write and send the posts means the announcement goes out while the change is still fresh, and each network gets a version that fits its limits.

Honest limits

  • No undo on some networks. A published post on Threads, TikTok or YouTube cannot be deleted through the API.
  • Media requirements. Instagram, TikTok and YouTube Shorts have no text-only post, and YouTube Shorts takes exactly one vertical video.
  • Character limits. X 280, Bluesky 300, Threads 500. 1Social flags drafts that run over before sending.
  • Facebook Pages only. Personal profiles cannot be posted to through Facebook's API.
  • Agent, not cron. Codex posts when you ask. For posts at a set time, schedule them in 1Social (Pro plan), which holds and sends them even if your laptop is closed.

Get started

Sign up at 1social.dev/login, add two lines to config.toml, run codex mcp login 1social, and let Codex announce your next release. Setup for other clients is on the 1Social MCP page.

Frequently asked questions

Where does Codex store MCP servers?

In ~/.codex/config.toml, or in .codex/config.toml inside a trusted project. The Codex CLI, the IDE extension and the ChatGPT desktop app share this configuration.

How do I sign in to an MCP server in Codex?

Add the server under [mcp_servers.name] with its url, then run codex mcp login with the server name. For 1Social that is codex mcp login 1social.

Can I limit which 1Social tools Codex can use?

Yes. Use enabled_tools or disabled_tools in the server's config.toml section to allow only the tools you want.

Will Codex post on a schedule by itself?

No. Codex posts when you ask. To publish at a set time, schedule the post in 1Social on the Pro plan, which sends it even if your laptop is closed.

Which networks can Codex post to through 1Social?

Instagram, TikTok, LinkedIn, X, Bluesky, Threads, Facebook Pages and YouTube Shorts.