Social media publishing
for your AI assistant.

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.

PostDelegate exposes a Streamable HTTP MCP server. Copy its URL from Settings → API Keys. The MCP path has no trailing slash.

https://YOUR-WORKSPACE-HOST/api/v1/mcp

MCP accepts a scoped API-key bearer token or an OAuth authorization supported by your client. OAuth acts with the signed-in user’s current permissions; it is not automatically draft-only.

• For an API key, select the intended workspace and connected-account allowlist.
• Begin with create_posts. Add upload_media or view_analytics only for workflows that need them.
• Leave publish_directly disabled for a draft-only API key. Keep credentials in client credential settings, not prompts or shared files.
• A client-side tool allowlist is an extra control; it does not replace workspace permissions.

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.

Attach workspace MediaAsset IDs. For uploads, use upload_media for supported small payloads, or request_media_upload, upload bytes to the returned URL, then finalize_media_upload. Follow the returned size and validation requirements.

• Do not use arbitrary media URLs where a media_asset_ids list is expected.
• MCP create_draft does not currently accept an idempotency_key. If its response is lost, check the web workspace before creating another draft.
• If you need retryable create requests with an idempotency key, use the documented REST create endpoint.
• Connecting MCP does not include an AI generation service or install a PostDelegate CLI.