Head to head · Social posting · October 2026 research run

Mixpost API + MCP vs Post Bridge API + MCP

Mixpost API + MCP scores 55.2 (C) on agent readiness against Post Bridge API + MCP's 44.1 (E), and leads in 5 of 7 scored categories. Post Bridge API + MCP leads on agent ergonomics and payments & pricing. Both do social posting.

Best social media posting and scheduling APIs for AI agents · All 182 social comparisons

Which one, for what

Mixpost API + MCP C

Best for Agencies and teams that must keep tokens and content on their own servers and want a one-off price.

Ahead on

  • Reliability, 70 against 42
  • Security & auth, 57 against 44
  • Maintenance & community, 63 against 31
  • Transparency & trust, 51 against 45

Also in its favour

  • Open source
  • No incidents deducted, where Post Bridge API + MCP loses 3 points for them

Watch for

No API or MCP in the free Lite edition, and Cloud's trial needs a card

Post Bridge API + MCP E

Best for Solo builders and small teams who want an agent to schedule and publish to 10 networks through OAuth for a flat price.

Ahead on

  • Agent ergonomics, 60 against 43
  • Payments & pricing, 23 against 15

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

Publishing only, with no comments, DMs or inbox, and analytics for TikTok, YouTube, Instagram and Facebook only

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Mixpost API + MCP +32

Mixpost API + MCP 63

Pro v7.3.1 on 3 November 2026 (30). Twenty Pro releases from v7.0.0 on 26 September to v7.3.1 on 3 November, more than three in the last 90 days (20). The public Lite tracker showed no maintainer replies on recent issues on 1 October and couldn't be re-read; Pro support is private (8). No official SDKs or registry entry (0). Lite has CI but last released 2.6.0 on 13 March 2026, and its last commit is 16 March 2026 (5). 30 + 20 + 8 + 0 + 5 = 63.

Post Bridge API + MCP 31

Recency from postbridge-cli 1.1.4, published to npm on 9 September 2026 per the 1 October reading of the npm registry (not re-read), 56 days before this check (20; 30 on 1 October). The repository bumps the CLI to 1.1.5 (4 October), 1.1.6 (19 October), 1.1.7 (25 October) and 1.1.8 (31 October) in commits with no tag and no changelog entry, which this run doesn't count as releases, so fewer than three confirmed releases or dated changelog entries fall in the 90 days from 6 August (0; 20 on 1 October, which also counted the MCP registry's versions). llms.txt says support is answered by the founder within a few hours. The repository has never had a pull request and there's no public changelog (8). The 1 October registry line rested on the official MCP registry's JSON API, which this run doesn't use, and the vendor publishes no official SDK (0; 15 on 1 October). The CLI has no dependencies and the repository runs no CI (3). 20 + 0 + 8 + 0 + 3 = 31.

Reliability Mixpost API + MCP +28

Mixpost API + MCP 70

Scored on the checklist for software you run yourself, since Pro installs into your own Laravel app and its uptime is whatever your server gives it. Mixpost Cloud has no public status page we could find. Installs from Inovector's Composer repository with PHP 8.2 or later stated, per the 1 October check (20). Lite runs a public test workflow on PHP 8.2 and 8.3, and Pro's CI isn't public; kept at the earlier partial value (10). The Lite repository's issues were read on 1 October (27 open, no maintainer replies visible) and couldn't be re-read on 4 November, and Pro's tracker is private (10). Release notes per version, with v7.0.0 flagged as breaking and no breaking change found in the 7.1 to 7.3 notes (15). Past 1.0, at Pro v7.3.1 (15). 20 + 10 + 10 + 15 + 15 = 70.

Post Bridge API + MCP 42

No readable status page. On 4 November 2026 status.post-bridge.com answered its robots.txt request with a redirect to a sign-in page, so the host is read as blocked and the 1 October reading of it is struck (0). No incident history to read (5). The OpenAPI document embedded in the API reference page, re-read on 4 November, sets 10 requests a second per key and one analytics sync per account every 30 minutes (15). The reference says to throttle and retry 429 responses with backoff, the analytics sync documents its own 429, and the agent skill says posts that report a platform 500 often publish anyway, so check results before republishing. That is backoff and safe-retry guidance without idempotency keys (12; the 1 October 5 wasn't a checklist value). No SLA found (0). The API and MCP aren't labelled beta (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.

Agent ergonomics Post Bridge API + MCP +17

Mixpost API + MCP 43

31 MCP tools since v7.3.0 added list-mentions on 30 October 2026, with no toolsets (5). A workspace role decides which tools a token may use, but the docs say a Viewer calling a members-only tool gets an error, not a shorter tool list, so nothing comes back (5 of 25). Some list endpoints paginate and some don't, per the API docs (12). Laravel-style JSON errors with field messages and 422 for validation, and MCP inputs with unknown option keys rejected with an error naming the accepted keys (15). No idempotency keys, and the read, write and destructive labels live in the docs rather than as MCP annotations. unschedule-post and restore-post give safe ways back (6). No official SDKs, only an n8n community node (5). 5 + 12 + 15 + 6 + 5 = 43.

Post Bridge API + MCP 60

16 compact MCP tools with no toolsets (15). Offset and limit with a next URL, and posts filter by platform and status (20). Errors are plain strings with no codes, though list_post_results gives per-platform outcomes and the skill maps common failure causes (12). No idempotency key and no annotations we could see. is_draft holds a post, and delete_post only touches scheduled or draft posts (6). A zero-dependency Node CLI and no SDKs. Omitting scheduled_at publishes at once (7). 15 + 20 + 12 + 6 + 7 = 60.

Security & auth Mixpost API + MCP +13

Mixpost API + MCP 57

Personal keys as Bearer headers that expire after 7, 30, 60 or 90 days, a year, a custom date or never, and since Pro v7.1.0 (15 October 2026) can be renamed, re-dated and rotated, but have no scopes and carry the full authority of the user who made them. Each instance is also an OAuth 2.1 server with PKCE (S256 only), refresh tokens that rotate on every use, revocation and two scopes, api and mcp, which choose the surface but not what the token may do (25 of 30). A key or OAuth token from a Viewer-role user can only read, and a workspace that requires post approval puts posts scheduled through MCP into needs-approval. Deletes aren't gated (15 of 20). Tools return the operator's own posts and analytics, little untrusted text (10). Connected apps can be reviewed and disconnected; no audit log found (0). The Lite repository's SECURITY.md asks for reports by email, with no acknowledgement time, which this run reads as 7. The path traversal (24 February 2026) and XSS (17 June 2026) reports on the Lite repository have no fix; the XSS is CVE-2026-57958, a Medium assigned by VulnCheck (7 of 20). 25 + 15 + 10 + 0 + 7 = 57.

Post Bridge API + MCP 44

The hosted MCP does OAuth 2.0 with PKCE (S256), automatic client registration and six scopes, among them posts:read, analytics:read, accounts:read and media:read, per the 1 October reading of its published OAuth metadata. It also takes a pb_live_ key as a Bearer header, and the MCP docs, re-read on 4 November, document ?key=pb_live_... for clients without header support and a Grok route with the key in the URL, so less 10 (20). Read-only scopes are possible and is_draft holds posts for review. The skill tells the agent to confirm local file and cron actions with the user (12). Tools return the operator's own posts and analytics, with no inbox or comments (10). list_post_results shows per-platform outcomes, no audit log (2). www.post-bridge.com/.well-known/security.txt returns 404, and no disclosure route or certification was found, only support@post-bridge.com (0). 20 + 12 + 10 + 2 + 0 = 44.

Payments & pricing Post Bridge API + MCP +8

Mixpost API + MCP 15

No x402 (0). Pro is $299 once and Enterprise $1,199 once, and Cloud's Momentum plan with the API and MCP is $49 a month, all public, with no per-call price (10). Lite is free but has no API or MCP, Pro has a 14-day money-back guarantee, and Cloud's 7-day trial needs a card (0). A person has to buy a licence or sign up for Cloud in a browser (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Post Bridge API + MCP 23

No x402 or other machine payment (0). Plan prices are public with $1 a month per account above 99, and no per-call price (10). The pricing FAQ, re-read on 4 November, still says free users get 5 posts a month, but the plan table shows only paid plans and doesn't say free users get the API. The 7-day trial reads $0.00 due today with no statement on cards, so part credit (5). A person signs up in a browser, or approves OAuth in a client (0). 0 + 10 + 5 + 0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Transparency & trust Mixpost API + MCP +6

Mixpost API + MCP 51

The API and MCP live in Pro and Enterprise, which are proprietary with clear licence terms and a perpetual fallback licence. Lite is MIT (15). Privacy policy from INOVECTOR DIGITAL S.R.L. of Moldova names Hetzner, DigitalOcean, PayPal and Sentry, but has no date, no DPA and vague retention (12). v7.0.0 is flagged breaking and the MIXPOST_CORE_PATH default change is documented, with no formal deprecation policy (8). Cloud subprocessors and countries named. We found no statement on whether self-hosted installs report anything back (10), per the 1 October check. 15 + 12 + 8 + 10 = 45.

Post Bridge API + MCP 45

The CLI, skills and plugin are MIT. The hosted service runs under terms that name only Post Bridge with Canadian governing law, no company type or registration, and a 24-hour refund window that the pricing FAQ gives as 7 days. The terms' Last Updated line showed the day of each check, 1 October and 4 November 2026 (10). The privacy policy, updated 5 October 2026, sets retention per data type, deletes personal data within 30 days of account deletion and names Supabase, Cloudflare, Stripe, Trigger.dev, Mailgun, Unkey and Vercel, with no DPA and no data locations (20). No deprecation policy. The terms promise email notice of changes (3). Subprocessors named, locations not (12). 10 + 20 + 3 + 12 = 45.

Score by category

CategoryWeightMixpost API + MCPPost Bridge API + MCPEdge
Reliability16%7042Mixpost API + MCP +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7672Mixpost API + MCP +4
Agent ergonomics13%4360Post Bridge API + MCP +17
Security & auth14%5744Mixpost API + MCP +13
Payments & pricing10%1523Post Bridge API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6331Mixpost API + MCP +32
Transparency & trust7%5145Mixpost API + MCP +6
Negative events≤150-3
TotalC 55.2/100E 44.1/100

Facts side by side

FactMixpost API + MCPPost Bridge API + MCP
KindHTTP APIHTTP API
VendorMixpost (Inovector)Post Bridge
Hosted endpointno (local only)https://api.post-bridge.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthTokenOAuth or key
PricingPaidPaid
x402nono
Licenceproprietary (Pro and Enterprise, which carry the API and MCP), MIT (Lite)MIT
Tools exposed3116
Read-only variant documentednoyes
llms.txtnoyes
MCP registrynot listedio.github.jackfriks/post-bridge
Last release2026-11-032026-09-09
Terms last updatedno date given2026-10-07
Privacy policy last updatedno date given2026-10-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity3.7k stars17 stars, 51 npm/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Post Bridge API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Mixpost API + MCP

Pro is a one-off $299 licence with unlimited accounts, an OpenAPI 3.1 file and a 31-tool MCP server on your own server, with OAuth 2.1 sign-in for MCP clients since October 2026. Personal keys have no scopes, the free Lite edition has no API or MCP, and two security reports on Lite remain unfixed.

Post Bridge API + MCP

Post Bridge publishes and schedules posts to ten networks through a REST API with a published OpenAPI document and a hosted MCP server with OAuth scopes, for a flat $39 a month. It has no inbox or comment tools and no readable status page, and the MCP also accepts the API key in the URL.

Before you call either

Mixpost API + MCP

  1. Call list-workspaces first. Workspace endpoints sit under /api/{workspaceUuid}
  2. Connect MCP clients by OAuth where the instance allows it, so no personal key is pasted into the client
  3. Create the key as a Viewer-role user when the agent only needs to read
  4. Use unschedule-post rather than delete-post when a person wants a post pulled back to draft
  5. Name the extra fields you need in get-post's include argument. Media details and options are left out by default

Post Bridge API + MCP

  1. Call list_social_accounts first, upload media, then create_post. Omit scheduled_at to publish at once
  2. Check list_post_results before republishing a failed post, since platform 500s often publish anyway
  3. Set is_draft true when a person should approve the post
  4. Put links for X in a reply unless the account has the Links in X posts add-on
  5. Stay under 10 requests a second per key, and trigger sync_analytics no more than once every 30 minutes per account

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Mixpost API + MCP or Post Bridge API + MCP?

Mixpost API + MCP scores 55.2 (C) on agent readiness against Post Bridge API + MCP's 44.1 (E), and leads in 5 of 7 scored categories. Post Bridge API + MCP leads on agent ergonomics and payments & pricing.

Do Mixpost API + MCP and Post Bridge API + MCP need an API key?

Mixpost API + MCP needs an access token. Post Bridge API + MCP takes an API key or an OAuth sign-in.

Can an agent call Mixpost API + MCP and Post Bridge API + MCP without installing anything?

No hosted endpoint is listed for Mixpost API + MCP. Post Bridge API + MCP has a hosted endpoint at https://api.post-bridge.com/v1.

Are Mixpost API + MCP and Post Bridge API + MCP open source?

Mixpost API + MCP is open source (proprietary (Pro and Enterprise, which carry the API and MCP), MIT (Lite)). No open-source release is listed for Post Bridge API + MCP.

Other comparisons with Mixpost API + MCP or Post Bridge API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.