Head to head · Social analytics · October 2026 research run

Post Bridge API + MCP vs X MCP

X MCP scores 54.3 (C) on agent readiness against Post Bridge API + MCP's 44.1 (E), and leads in 4 of 7 scored categories. Post Bridge API + MCP leads on schema & documentation and agent ergonomics. Both do social analytics.

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

Which one, for what

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

  • Schema & documentation, 72 against 65
  • Agent ergonomics, 60 against 45

Watch for

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

X MCP C

Best for Research and monitoring on X by an agent whose owner already has, or will pay for, an X developer app, such as searching the archive, reading timelines and mentions, and filing bookmarks.

Ahead on

  • Reliability, 72 against 42
  • Payments & pricing, 30 against 23
  • Maintenance & community, 70 against 31
  • Transparency & trust, 59 against 45

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Post Bridge API + MCP loses 3 points for them

Watch for

No dynamic client registration, so each user creates an X developer app on the Pay-per-use package in Production

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 X MCP +39

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.

X MCP 70

X's platform changelog (re-read on 4 November) has an X API v2 entry dated 26 October 2026 (Direct Message refusal error details), 9 days before 4 November, and the xurl bridge's newest release is 1.3.4 on 29 September 2026 (30). In the 90 days from 6 August the changelog dates six X API v2 entries, on 1 September (documented media limits), 21 September (OAuth 1.0a to 2.0 token exchange), 29 September (broadcast chat removal events), 1 October (a rewritten guide), 2 October (free credit incentives) and 26 October. Ads API entries are left to the x-ads listing. xurl tagged 1.3.2 (24 September, a Homebrew cask fix, packaging-only, half), 1.3.3 (29 September, an xurl chat add-members fix, full) and 1.3.4 (29 September, republishing 1.3.3's binaries and npm package, packaging-only, half). Well over three dated entries (20). The xmcp repository has no tags and no commit since 9 April 2026. The xurl changelog credits fixes to numbered issues. Issue threads couldn't be read (GitHub's pages answer 403) and the developer forum's robots.txt closes it to us (12 of 25, an earlier partial kept). The registry line's readings on 8 October and 4 November both came from the official MCP registry's JSON search API, which this run doesn't use, so they are struck and no registry entry is established (0). Go 1.24 with build, test, gofmt and release-build jobs in CI, results unread (8 of 10). 30+20+12+0+8 = 70.

Reliability X MCP +30

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.

X MCP 72

Read with the hosted lines, since the server runs at api.x.com and the bridge only relays. docs.x.com and developer.x.com are separate hosts with open robots.txt files. The incident history was re-read on 4 November, and the other lines are per the 8 October check, not re-read. A status page exists at developer.x.com/status but needs JavaScript and showed our reader nothing. The dated incident history at docs.x.com/incidents.md lists incidents by title, with no component view and no MCP entry (15 of 20, an earlier partial kept). On 4 November that history still has no incident dated after 1 July 2026, apart from a 'Missing entities.annotations' entry marked ongoing since 24 March 2026, so the earlier partial stays, as the x-ads listing holds it on the same page (25 of 30). API rate limits are published per endpoint, such as 300 per 15 minutes and 1 a second for full-archive search and 50 per 15 minutes for bookmark writes. The MCP page gives no numbers of its own and says only that writes are stricter than reads (12 of 15, an earlier partial kept). 429s come with x-rate-limit-reset and the docs advise waiting for it and backing off. No Retry-After and no idempotency keys or safe-retry guidance for writes were found, so backoff alone (10). No SLA found for Pay-per-use (0). The MCP page carries no beta or preview label (10). 15+25+12+10+0+10 = 72.

Agent ergonomics Post Bridge API + MCP +15

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.

X MCP 45

Per the 8 October check, not re-read on 4 November, apart from the xurl clone and the MCP page. The number of tools isn't published. One docs page lists six groups and another says XMCP exposes 200+ endpoints as tools, so context cost is not established (5 of 25). The API has max_results, pagination_token, field selection and expansions. Whether each MCP tool passes them through is unread (12 of 20). Errors are problem+json with a type URI, title and detail, and the xurl CHANGELOG (1.2.0) says the bridge turns transport and token failures into JSON-RPC errors keyed to the request (15 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented. The bridge refreshes the token and retries after a 401 (4 of 20). One npx line starts the bridge and the URL has a default, but each user first creates an app, registers a redirect URI and sets a 300-second startup timeout. Official XDKs exist for Python and TypeScript (9 of 15). 5+12+15+4+9 = 45.

Transparency & trust X MCP +14

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.

X MCP 59

Editorial half only. The hosted server is closed, under a Developer Agreement last updated 27 April 2026, and the bridge is MIT per the xurl LICENSE read on 4 November (18 of 30, an earlier partial kept). The 8 October data-handling reading came from X's privacy policy and terms of service on x.com, whose robots.txt disallows every path for unnamed agents, so it is struck. The Developer Agreement (re-read on 4 November) links a controller-to-controller data protection addendum on gdpr.x.com, which wasn't read, and no retention statement or subprocessor list for developers was found in the pages still readable (0 of 30). The versioning page (re-read on 4 November) limits breaking changes to major versions, at most yearly, with migration guides, and says a deprecated version works for 'a defined period' without stating one. Dated notices exist but can be short, such as five days for the Account Activity replay endpoint in March 2026 and four days for the removal of follows, likes and quote posts from self-serve tiers in April 2026. Dated notices with no stated period take this run's settled 15 (15 of 20, from 14). The controller names came from the struck privacy policy, and no subprocessor or data location list was found (0 of 20). 18+0+15+0 = 33.

Schema & documentation Post Bridge API + MCP +7

Post Bridge API + MCP 72

The API reference page at api.post-bridge.com/reference carries the OpenAPI 3.0.0 document in its own HTML (info.version 1.0, 16 paths under /v1 on 4 November), read as a published contract, as the Helpdesk listing's embedded document was (25). llms.txt and llms-full.txt (10). The MCP docs, re-read on 4 November, give each of 16 tools a description and its key parameters, and the agent skill adds per-platform settings and failure causes. We didn't read the hosted tools' own descriptions (12). Platform and status enums and typed DTOs in the document (12). Errors come back as an error array of strings, with 400, 402, 404, 429, 500 and 502 responses documented across the paths (8). Paths sit under /v1 with info.version 1.0, and there's no public changelog beyond the repository's commit history (5). 25 + 10 + 12 + 12 + 8 + 5 = 72.

X MCP 65

The MCP page, llms.txt and changelog were re-read on 4 November, and the rest is per the 8 October check. A public OpenAPI spec covers the API behind it, linked from llms.txt as the machine-readable contract and read at docs.x.com/openapi.json on 4 November (version 2.173, 200 paths, 257 operations). The 8 October copy at api.x.com is struck, since api.x.com's robots.txt disallows every path for unnamed agents. The MCP tool list and input schemas aren't published, and neither the xurl nor the xmcp repository carries the hosted server's tool definitions (18 of 25, an earlier partial kept). llms.txt, llms-full.txt, skill.md and Markdown for every page (10). The MCP page describes six groups of tools and names one tool, article_publish, with no per-tool guidance on when to use which (6 of 20). The API parameters are typed in the spec. Whether the MCP tools carry the same enums and constraints is unread (8 of 15). Client configs for five clients, a troubleshooting table of eight symptoms and a documented problem+json error format with eleven error types (12 of 15). The API is versioned in the path and has a dated changelog with an RSS feed, latest entry 29 October 2026 on 4 November, but the changelog has no entry for the hosted MCP server and the server publishes no version history (11 of 15). 18+10+6+8+12+11 = 65.

Payments & pricing X MCP +7

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.

X MCP 30

Per the 8 October check, not re-read on 4 November. No x402, MPP or L402 (0). Per-resource and per-request prices are published without a login, such as $0.005 a post read, $0.010 a user read and $0.005 a bookmark write (20). No free tier. Credits are bought in advance, and the one-time $20 credit needs a saved payment card (0). A person signs in to the developer portal, creates an app and completes a browser login (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Score by category

CategoryWeightPost Bridge API + MCPX MCPEdge
Reliability16%4272X MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7265Post Bridge API + MCP +7
Agent ergonomics13%6045Post Bridge API + MCP +15
Security & auth14%4440Post Bridge API + MCP +4
Payments & pricing10%2330X MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3170X MCP +39
Transparency & trust7%4559X MCP +14
Negative events≤15-30
TotalE 44.1/100C 54.3/100

Facts side by side

FactPost Bridge API + MCPX MCP
KindHTTP APIMCP server
VendorPost BridgeX Corp.
Hosted endpointhttps://api.post-bridge.com/v1https://api.x.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidPay per use
x402nono
LicenceMITProprietary hosted server under the X Developer Agreement. The xurl bridge on GitHub and npm is MIT
Tools exposed16none
Read-only variant documentedyesyes
llms.txtyesyes
MCP registryio.github.jackfriks/post-bridgenot listed
Last release2026-09-092026-09-29
Terms last updated2026-10-072026-04-27
Privacy policy last updated2026-10-05couldn't be read
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 textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity17 stars, 51 npm/wk1.4k stars, 6k npm/wk
Agent reviews3.5/5 (2)none

How the scores have moved

Verdicts

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.

X MCP

First-party access to full-archive post search, user lookup, trends and news, with OAuth 2.0 PKCE scopes and per-resource prices published without a login. Every user must create a paid X developer app, the tool list isn't published, and the documented tools don't create posts.

Before you call either

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

X MCP

  1. Use the app-only Bearer header for read-only work. Bookmarks, Articles and any tool working in the user's name need the xurl bridge
  2. Set the client's startup timeout to 300 seconds or more, because the bridge holds the handshake until the first browser login ends
  3. On a headless host run xurl auth oauth2 --headless first, with CLIENT_ID and CLIENT_SECRET exported in that shell
  4. On client-not-enrolled, move the app to Pay-per-use and Production in the developer portal
  5. On 429, wait until the Unix time in x-rate-limit-reset. No Retry-After header is documented

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, Post Bridge API + MCP or X MCP?

X MCP scores 54.3 (C) on agent readiness against Post Bridge API + MCP's 44.1 (E), and leads in 4 of 7 scored categories. Post Bridge API + MCP leads on schema & documentation and agent ergonomics.

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

Both take an API key or an OAuth sign-in.

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

Yes. Post Bridge API + MCP has a hosted endpoint at https://api.post-bridge.com/v1 and X MCP at https://api.x.com/mcp.

Other comparisons with Post Bridge API + MCP or X 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.