Connect your AI to Post Bridge

When you need an API key

Only in three cases: a client with no OAuth support (Grok and other URL-only connectors), headless or server-side agents where nobody can click a login window, and scripts hitting the REST API or CLI. Everything else should use OAuth — it's one click, and revoking it doesn't break your other integrations.

Keys come from the API Keys page and go in a header:

Authorization: Bearer pb_live_your_api_key_here

OAuth connections are managed separately, under Settings → Connected apps. Revoking either takes effect immediately.

Example prompts

Once connected, talk to your agent normally. It picks the right tools on its own. A few things to try:

• Which social accounts do I have connected?
• Post “shipping something new today” to my X and LinkedIn accounts right now.
• Schedule this video to TikTok, Instagram Reels and YouTube Shorts for tomorrow at 9am.
• Show me everything I have scheduled this week.
• Move my Friday post to Monday morning and shorten the caption.
• Which of my posts got the most views in the last 30 days?

Sane default for agent-written content: ask for drafts first, review in the dashboard, then schedule. Nothing publishes behind your back.

Tool Reference

The MCP server exposes 13 tools. Your AI will discover these automatically — you just ask in plain language.

Media requirements by platform

Attach media with media (uploaded media IDs) or media_urls (public URLs). Some platforms can't publish a text-only post and will fail if none is attached. You can create a post with no media and add it later with update_post, but it won't publish to a media-required platform until the media exists.

When a post targets several platforms, each takes what it supports from the post's media; anything a platform can't use is skipped for that platform.

Platform configurations

create_post and update_post take an optional platform_configurations object to override caption/media or set platform-specific options. Each override is keyed by platform name — only add a key for a platform you're actually posting to, and only the fields you want to override (everything else falls back to the top-level caption/media).

{
  "caption": "New drop is live 🎉",
  "social_accounts": [44029, 44031, 44032],
  "platform_configurations": {
    "tiktok":   { "draft": true },
    "instagram": { "video_cover_timestamp_ms": 2000 },
    "twitter":  { "first_comment": "Grab it: https://example.com/drop" }
  }
}

Enums accept only the exact values shown. The MCP tool schema carries the full per-field help, so your AI assistant sees these descriptions inline when it calls the tool.

Good to know

• Drafts — is_draft saves the post in Post Bridge only. It does not create a draft on any social platform. When you later publish the draft, all platforms post immediately.
• Media cleanup — media files are automatically deleted after all posts using them have published. If you share the same media across multiple drafts or scheduled posts, it stays available until the last one goes out. After that, the media ID becomes invalid.
• Deleting posts — you can only delete scheduled or draft posts. Published posts cannot be deleted via the API.
• Revoking access — OAuth connections live under Settings → Connected apps, API keys under API Keys. Revoking either disconnects immediately.