Give Codex a controlled social publishing workflow with MCP
The useful integration between Codex and social media is not “Codex can post.” It is a controlled, observable workflow: Codex receives access to a limited PostSider tool surface, reads the real channels, proposes content, and saves one draft you authorize.
This is a setup tutorial, not a fabricated live demo. The exact Codex client login experience may vary by installation; the remote server URL and CLI configuration can be verified independently. The MCP landing page covers the supported connection options in one place.
1. Register the remote server in Codex
codex mcp add postsider --url https://mcp.postsider.com/mcp
codex mcp list
The same server can also be added to your trusted Codex config.toml:
[mcp_servers.postsider]
url = "https://mcp.postsider.com/mcp"
Complete OAuth authentication when the client asks for it. Carefully inspect the workspace and requested scopes. If you only need channel enumeration, don’t grant write access. The remote OAuth approach is distinct from running npx -y @postsider/mcp locally with POSTSIDER_API_KEY: never paste a key into a remote URL.
Codex documents this command pattern in the official MCP setup guide. PostSider’s developer setup examples include both Claude and Codex.
2. Ask for a read-only verification
With the PostSider MCP connection, list the connected social channels.
Report each channel's name, platform and ID.
Do not create or change any post, calendar entry or connection.
If a request fails, show the error; don't assume success.
Compare the returned IDs to your PostSider dashboard. This matters when a workspace has a personal LinkedIn account, a company page and multiple X accounts.
3. Turn a coding result into a reviewed draft
A practical developer workflow is converting a release note into proposed social copy, not letting the agent automatically post after a commit.
Summarize the CHANGELOG section I selected into a concise release note.
Show the proposed exact caption and the PostSider channel you will use.
Do not include repository secrets, private issues or customer data.
Wait for my explicit approval.
After approval, save exactly one PostSider draft (type=draft).
Return the postId from the create response. Then read that same postId
and verify the state is DRAFT and the channel and text match.
Do NOT schedule, publish, bulk-cross-post or post immediately.
If Codex cannot call the MCP write tool, first verify that its OAuth grant includes the required scope and that your workspace plan and channel permissions permit the operation. Do not bypass authorization by pasting a more privileged token.
4. Review before any future publishing operation
A saved draft should be visible in the shared PostSider calendar. A later schedule or publish operation is a separate decision with platform-specific validation, timezone handling and potentially formal team approval. A “tool call succeeded” message does not imply a public post was delivered.
For REST-only release pipelines, the one API walkthrough explains the nested PostSider payload and idempotent retries. For an importable no-publishing workflow, use n8n’s verified-draft example.
Recording a truthful demo
Show codex mcp list, connected remote MCP, the actual channel list, the exact human-reviewed caption, the create response’s post ID, and the matching saved DRAFT state. Hide credentials and client account information. Capture the unedited error if a step fails; do not reconstruct a fake success screenshot.
Frequently asked questions
How do I connect the Codex CLI to PostSider's hosted MCP server?
Use codex mcp add postsider --url https://mcp.postsider.com/mcp and check with codex mcp list. Authenticate using the client's supported OAuth sign-in if prompted.
Do I put my PostSider API key into Codex config.toml for hosted MCP?
No. The hosted MCP flow uses OAuth. A raw organization API key is only for the separate local stdio package or REST integration.
Does a Codex MCP draft appear on social networks automatically?
No. A draft is stored in PostSider, not published. Read back the returned postId, verify the saved DRAFT state and review it in the calendar before any separate schedule/publish operation.