Register PostSider as an MCP server
Add the local stdio server with Codex so the client can discover PostSider tools during a session.
Codex + PostSider MCP
Connect Codex to social media with MCP
Codex only needs one MCP server to work with the social accounts already connected in PostSider. Start by listing channels, then move on to drafts and scheduling.
Start with the social media scheduler API or browse the full developer platform.
How it works
Set up the server, verify it, then let Codex use the tools.
The social OAuth connections stay in PostSider. Codex gets a small tool surface over MCP instead of a pile of provider credentials.
Give the server the PostSider API key
Pass POSTSIDER_API_KEY to the MCP process. Codex does not need separate credentials for LinkedIn, X or the other connected networks.
Ask Codex to inspect channels first
A useful first test is listing connected channels. If that works, the MCP server is running and authenticated.
Draft or schedule from the same session
Codex can then use the discovered publishing tools while you keep the resulting posts visible in the PostSider calendar.
Concrete example
Current Codex CLI setup for a local stdio MCP server
The command shape matches the current Codex MCP CLI: server name, environment variables, then the stdio command after --.
codex mcp add postsider \
--env POSTSIDER_API_KEY=your-api-key \
-- npx -y @postsider/mcp
codex mcp listRelated developer guides
Go deeper where your workflow needs it.
Full Codex setup guide Read the longer walkthrough for configuration, first tool calls and a draft-first workflow. Read more → PostSider MCP server See how the MCP layer maps agent tool calls onto the PostSider publishing system. Read more → REST or MCP for an agent? Use REST for deterministic orchestration and MCP when the client should discover tools. Read more →
FAQ
Common questions.
Can Codex use PostSider through MCP?
Yes. Codex supports MCP server configuration, including local stdio servers, and PostSider exposes its publishing tools through an MCP package.
Does Codex need credentials for each social network?
No. Connect social accounts in PostSider once. Codex only needs access to the PostSider MCP server and its PostSider API credential.
Can the configuration be project-specific?
Yes. Current Codex supports MCP configuration in the normal Codex config and project-scoped .codex/config.toml for trusted projects.
Can Codex schedule posts rather than publish immediately?
Yes. Use the discovered PostSider tools to create drafts or scheduled posts and keep the calendar available for review.