Skip to main content
Post Bridge’s MCP server lets Notis schedule and publish social posts, upload media, and retrieve analytics across your connected social accounts — while Notis stays responsible for content creation, review, and approval.

​
What this setup does

In this setup, Notis handles the AI work: generating post ideas, drafting captions, creating images, reviewing outputs, and deciding when content is ready to publish. Post Bridge handles the publishing actions through MCP: listing accounts, creating/scheduling posts, uploading media, and fetching analytics.
That split is important: Notis is your creation and validation layer, while Post Bridge is your execution layer for social publishing.

​
Prerequisites

  • An active Post Bridge subscription
  • At least one connected social media account in Post Bridge
  • (For most MCP clients) A Post Bridge API key

​
Post Bridge MCP connection

Post Bridge offers a hosted MCP endpoint, so there is nothing to install. You authenticate with your Post Bridge API key as a Bearer token.

​
Step 1: Connect social accounts in Post Bridge

  1. Log in to Post Bridge.
  2. Connect at least one social media account.
  3. Confirm the account appears in your social accounts list (you’ll verify again via MCP later).

​
Step 2: Get your Post Bridge API key

  1. Open the API Keys dashboard in Post Bridge.
  2. Create a new key (or copy an existing one).
  3. Keep it secure — Notis will use it to authenticate against Post Bridge.

​
Step 3: Add Post Bridge as a custom MCP in Notis

Add an MCP server with these values:
  • Display Name: Post Bridge (or any name you’ll recognize)
  • Description: a few words on what it does. For example: “Schedules, publishes, and manages social media posts across connected accounts. It can upload media, schedule posts, and retrieve analytics.”
  • Server URL: https://www.post-bridge.com/api/mcp/mcp
  • Authentication: Headers, with the name Authorization and the value Bearer pb_live_your_api_key_here (your key from Step 2)

​
Step 4: Verify the connection

Useful first checks:
  1. List your connected accounts (to confirm Notis can see destinations).
  2. Create a draft or scheduled post (to confirm publishing flow works).
  3. List posts / analytics (to confirm read access).

​
Tool reference (11 tools)

Post Bridge’s MCP server exposes 11 tools. Your AI will discover these automatically — you just ask in plain language.

​
Example workflow: let Notis create, let Post Bridge publish

  1. Create the content in Notis — Generate the creative, storyboard, or image.
  2. Validate in Notis — Check brand voice, clarity, platform fit, and compliance.
  3. Upload media via Post Bridge — Use upload_media for assets hosted at a public URL.
  4. Create a scheduled post via Post Bridge — Use create_post with scheduled_at and the selected social_accounts.
  5. Check delivery — Use list_post_results after publishing.
  6. Review performance — Use sync_analytics then list_analytics.

​
Good to know

  • Drafts: is_draft saves the post in Post Bridge only. It does not create a native draft inside each social platform.
  • Media lifecycle: Media may be cleaned up automatically after the last post using it has published. If you reuse media across multiple scheduled posts, keep an eye on the lifecycle behavior.
  • Deleting posts: You can only delete scheduled or draft posts. Published posts cannot be deleted via the API.

​
Troubleshooting

  • Authentication fails: Confirm the API key is valid and sent as a Bearer token in the Authorization header.
  • No accounts found: Confirm you connected at least one social account in Post Bridge.
  • Posting fails: Use list_post_results to inspect platform-specific errors.

​
Summary

Post Bridge provides an HTTP MCP endpoint that Notis can connect to with a Bearer-authenticated API key. It exposes tools for listing social accounts, uploading media, scheduling/publishing posts, and retrieving analytics — enabling a workflow where Notis creates and validates content while Post Bridge executes publishing and measurement.