Social media publishing
for Codex.

These guides describe the implemented workspace protocols. Customer access and live platform publishing remain subject to launch availability. Use the endpoint from your own PostDelegate workspace, not the public marketing website. Examples use a placeholder origin.

Add the server below to your Codex config.toml. Replace the workspace hostname and make POSTDELEGATE_API_KEY available securely to the process running Codex. Your organization may manage these settings for you.

[mcp_servers.postdelegate]
url = "https://YOUR-WORKSPACE-HOST/api/v1/mcp"
bearer_token_env_var = "POSTDELEGATE_API_KEY"

Issue a PostDelegate API key for the intended workspace and accounts. Grant create_posts, and add upload_media only when needed. Leave publish_directly disabled for a draft-only connection. Do not commit the token to config.toml, a repository or a prompt.

• For a client using OAuth instead, follow its supported authorization flow. PostDelegate OAuth inherits the signed-in user’s authority.
• An MCP endpoint must be reachable from the environment executing the connection. Remote environments cannot use your laptop’s loopback address.
• No PostDelegate-specific Codex plugin, skill package or CLI installation is required by this protocol guide.

Use list_accounts to discover the connected accounts your client can access. If the list is empty, connect a supported account in the web workspace first.

List the accounts I can access and their capabilities. Ask which one to use. Turn my brief into one draft using create_draft. Do not schedule or publish. Return the post ID so I can review it in PostDelegate.

Complete required approval stages in the web workspace. Scheduling requires both create_posts and publish_directly. An approval requirement still applies when the actor has scheduling permission.

• Use schedule_draft with the existing post_id and an ISO 8601 scheduled_at timestamp, including its timezone offset or Z for UTC.
• schedule_post creates a new scheduled post. Do not use it as a substitute for scheduling an existing draft.
• Use get_post to inspect per-channel results. Scheduled means queued, not published.
• If the social platform’s outcome is uncertain, review the account before making another publishing attempt.

Have Codex return the post ID, selected account and draft status. Check that draft in the web workspace before enabling scheduling. A successful connector configuration does not establish that platform permissions or live publishing have been qualified for this deployment.

Create one draft for the account I select. Return its post ID and account. Do not schedule or publish. If the create response is uncertain, stop and tell me to check the workspace before retrying.