Codex CLI · config.toml · MCP
Social publishing for Codex workflows
Codex runs in your terminal and CI — PostSyncer gives it hands. Register the PostSyncer MCP server in Codex's config.toml and your agent can schedule posts, manage comments, and pull analytics across 11+ networks, scriptable end to end.
Connect Codex in three steps
-
1
Prepare PostSyncer
Connect the social accounts your automation should publish to and mint a personal access token in Settings → API Integrations. Scope it narrowly for unattended runs — posts plus read abilities is usually enough.
-
2
Register the MCP server in config.toml
Add PostSyncer under mcp_servers in ~/.codex/config.toml with the hosted MCP URL and your Bearer token. Codex loads the tool schemas on startup — no SDK or scraping required.
-
3
Automate the boring half of marketing
Run Codex interactively ("schedule this week's posts from content.md") or headless in CI: publish the release announcement whenever a tag ships, on every network at once.
MCP endpoint: https://postsyncer.com/mcp
— works as an OAuth connector or with Authorization:
Bearer <token>. Prefer raw HTTP? Use the
REST API.
What teams do with Codex + PostSyncer
Tools Codex can call
| Area | MCP tools |
|---|---|
| Workspaces |
list-workspaces
|
| Accounts |
list-accounts, delete-account
|
| Labels |
list-labels, create-label, get-label, update-label, delete-label
|
| Campaigns |
list-campaigns, create-campaign, get-campaign, update-campaign, delete-campaign
|
| Posts |
list-posts, create-post, get-post, get-post-by-url, get-post-by-platform-post-id, analyze-twitter-post, update-post, update-post-auto-plug, update-post-comment-moderation, update-post-contact-collection, delete-post
|
| Media |
list-media, get-media, upload-media-from-url, upload-media-file, delete-media
|
| Folders |
list-folders, create-folder, get-folder, update-folder, delete-folder
|
| Comments |
list-comments, sync-comments-from-platforms, create-comment, get-comment, update-comment, delete-comment, hide-comment
|
| Analytics |
get-analytics-summary, get-analytics-workspace, get-analytics-post, get-analytics-account, sync-post-analytics
|
Need column-by-column detail? See the tools reference in the API docs.
Using a different agent?
favorite accounts
Invest in
Growth
,
Not Just Tools
Simple pricing for creators, teams, and agencies.
No per-user fees. No hidden limits. Start free.
Starter Plan
For solo creators and freelancers
Pro
Growing teams and agencies
Pro Plus
Best ValueAdvanced AI tools for businesses and teams
Still deciding?
View full feature comparisonCompare all plans
See how each plan stacks up. All plans include a 7-day free trial.
Starter Plan
10
Pro
15
Pro Plus
30
Starter Plan
Unlimited
Pro
Unlimited
Pro Plus
Unlimited
Starter Plan
Unlimited
Pro
Unlimited
Pro Plus
Unlimited
Starter Plan
1 (add more anytime)
Pro
2 (add more anytime)
Pro Plus
3 (add more anytime)
Starter Plan
50 GB Storage
Pro
100 GB Storage
Pro Plus
Unlimited Storage
Starter Plan
Basic
Pro
Advanced
Pro Plus
Advanced
Starter Plan
Basic
Pro
Advanced
Pro Plus
Advanced
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
1,000/m
Pro
1,000/m
Pro Plus
2,000/m
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
1M+
Pro
2M+
Pro Plus
3M+
Starter Plan
Light
Pro
Moderate
Pro Plus
Heavy
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
✓
Pro
✓
Pro Plus
✓
Starter Plan
Live chat
Pro
Priority
Pro Plus
Priority
Frequently Asked Questions
Codex and PostSyncer — common questions
Add an entry under mcp_servers in ~/.codex/config.toml with the URL https://postsyncer.com/mcp and an Authorization: Bearer YOUR_TOKEN header. The token comes from Settings → API Integrations.
Yes — that's the point. Run Codex non-interactively with a prompt like "publish the release announcement for the new tag" and it will draft and schedule posts through PostSyncer. Store the token as a CI secret and scope it to only the abilities the job needs.
MCP gives the model typed tools it can reason over — good when Codex decides what to do. The REST API is better when your script decides and just needs execution. Both use the same token, accounts, and permission model, so you can mix them freely.
Have the job create posts as drafts or schedule them a few hours out so a human can review in the PostSyncer calendar. Use a narrowly-scoped token, and watch the first runs before letting it publish immediately.