Codex MCP serverfor social media scheduling
Add Posty as a Codex MCP server and turn release notes, changelogs and half-formed ideas into drafts, reviews and scheduled posts without leaving the terminal. Sign in with Posty. Your workspace permissions apply.
https://api.posty.social/mcp- Transport
- Streamable HTTP
- Sign in
- OAuth with your Posty account
- Permissions
- Your workspace role, checked per call
- Plans
- Growth and Accelerate
- Stored in
- ~/.codex/config.toml
Connect Codex in three steps
Posty is a remote MCP server. Codex adds it by URL, you sign in once in the browser, and every tool call after that runs with your own workspace permissions.
Official Codex MCP documentation- 1
Add the server
Run this in any terminal. Codex writes the server to its configuration, which the CLI, the IDE extension and the Codex app share, so you only add it once.
Codex setupcodex mcp add posty --url https://api.posty.social/mcp - 2
Sign in and approve access
Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. If setup did not already prompt you, start the sign-in yourself.
Authentication commandcodex mcp login posty - 3
Choose a workspace and start
Open a new Codex session and ask it to list your Posty workspaces. Name the one you want in each request. Codex shows connected servers and their tools when you run its MCP command inside a session.
Inside a Codex session/mcp
What Codex can do once it’s connected
Every tool mirrors one operation of the public API, so anything a script can do, your assistant can do, within your role. The server publishes its full tool catalog with every schema.
- Posts and scheduling
- Create drafts with text and settings per channel, move them onto the calendar, reschedule up to 50 at once and read delivery history.
create_postupdate_post_contentbulk_schedule_posts - Approvals
- Submit a post for review, approve it or request changes, and see who has been asked and how each ask ended. Approval rules stay in force.
act_on_postlist_post_review_requestsget_post_history - Media
- Upload images and video into the library, organise folders, set alt text and attach files to a post’s channels.
create_media_uploadreplace_post_content_mediaset_media_alt_text - Campaigns
- Create a campaign brief with objective, personas and dates, file posts under it and read its results against the brief.
create_campaignadd_post_to_campaignget_campaign_results - Analytics
- Workspace KPIs against the previous period, per post performance, audience demographics and the metrics each platform reports.
get_analytics_overviewget_analytics_detailget_post_native_metrics - Inbox
- Read comments and direct messages from connected channels, reply, assign a teammate and change a conversation’s status.
list_inbox_conversationslist_post_commentscreate_post_comment
Things to ask Codex
Replace “Launch” with your workspace name. Each one maps onto the tools above, and Codex shows you the calls before they run.
From a changelog to a draft
Example promptRead CHANGELOG.md, then draft a LinkedIn post about this release in my Launch workspace. Keep it as a draft for me to review.Fill the week
Example promptSchedule the three drafts in Launch for Tuesday, Thursday and Saturday at 9am local time, and tell me which channels each one goes to.Check what worked
Example promptIn Launch, which posts from the last 30 days got the most engagement, and what did they have in common?
Your workflow.
Still your call.
Posty checks workspace membership and permissions on every call. Drafts, approvals and scheduling follow the same rules as the app, and a token never freezes a permission you have since lost.
You can work across any workspace you have access to. Tell your assistant which one to use, review its drafts, and publish when you’re ready. See the roles and visibility matrix for what each role can do.
Questions about Posty and Codex
- Does the Codex IDE extension pick up the server too?
- Yes. The Codex CLI, IDE extension and app read the same configuration file, so a server added with the CLI appears in all of them. To keep a server to one repository, add it inside the project instead; Codex reads a project configuration only in trusted projects.
- Will Codex schedule or publish without asking me?
- Codex asks before running tools by default and lets you set an approval mode per server or per tool. Its mode that prompts only for tools not marked read-only fits Posty well, because every Posty tool declares whether it reads or writes. Posty applies your workspace permissions and approval rules on top.
- Which permissions does the assistant get?
- Exactly yours. Every tool call checks your workspace membership and role at that moment, so an assistant can only see the workspaces you belong to and do what you could do in the app. Approval rules still apply: a workspace that requires review before scheduling requires it from your assistant too.
- Which Posty plans include MCP access?
- The Growth and Accelerate plans, the same plans that include the public API. A workspace on another plan returns a clear plan error instead of connecting.
- How do I check or remove the connection?
- List configured servers with the Codex MCP list command, which shows each server and its state. Signing out in Posty or removing the server entry from the configuration file ends the connection; the next sign-in asks for approval again.
Use Posty from another assistant too
One server, the same sign-in and the same permissions in every client. Each one has its own guide.
Your assistant. Your workspace. Your rules.
Create a workspace, connect Codex and keep every post inside the approvals and permissions your team already uses.
MCP access is included on Growth and Accelerate, from $39 per workspace a month. Compare plans