Head to head · Social analytics · October 2026 research run

Metricool API + MCP vs X MCP

X MCP scores 54.3 (C) on agent readiness against Metricool API + MCP's 31.4 (F), and leads in 4 of 7 scored categories. Metricool API + MCP leads on security & auth, payments & pricing and transparency & trust. Both do social analytics.

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

Which one, for what

Metricool API + MCP F

Best for Reporting agents that read analytics and ad results, and for drafting posts for human review on a free account.

Ahead on

  • Security & auth, 48 against 40
  • Payments & pricing, 45 against 30
  • Transparency & trust, 66 against 59

Watch for

REST API only on Advanced ($67 a month) and Custom

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 15
  • Schema & documentation, 65 against 23
  • Agent ergonomics, 45 against 39
  • Maintenance & community, 70 against 6

Also in its favour

  • Runs on your own machine

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 +64

Metricool API + MCP 6

No dated API or MCP change found. mcp-metricool on PyPI was at 1.1.9 from 7 October 2025 per the 2 October check; pypi.org didn't resolve from our network on 10 November (0). No releases or dated changelog entries since 12 August (0). No public API changelog. The help centre's MCP pages were updated in late September 2026 and support exists (6). No official SDKs or registry entry (0). metricool/mcp-metricool, the repository the help centre names, still asks for credentials to clone on 10 November (0). The terms page footer links a Product Updates page, not read because the terms bar automated extraction. Total 6.

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 +57

Metricool API + MCP 15

status.metricool.com and its metricool.statuspage.io copy refused our reader in robots.txt on 1 and 2 October 2026, so the 30 September reading of the page is struck (0 of 20), and Metricool's terms now bar automated extraction, so the host wasn't requested on 10 November. No incident history we could read (5). No request rate limits published. The terms, updated 3 November 2026, say Metricool may monitor and rate-limit usage without giving numbers, and set 500 API calls a month per brand as "Standard Use" for the Integration and White Label plans, a billing threshold rather than a request limit (0). No 429 or retry guidance found (0). No SLA, and the terms promise only best efforts at round-the-clock access (0). The API and MCP aren't labelled beta, per the 2 October check, not re-read on 10 November (10). Total 15.

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.

Schema & documentation X MCP +42

Metricool API + MCP 23

The listing names an OpenAPI 3.0 file at app.metricool.com/api/swagger.json (553 paths per the 30 September check). It sits under the REST API's own base path and the docs page is a viewer drawn by script over it, so the 30 September reading is struck (0 of 25), and the typed-input credit that rested on it goes with it (0 of 15). llms.txt on the help centre, per the 2 October check (10). The help centre explains what the MCP can and can't do, and the hosted tools' definitions need an OAuth session (8). The errors page documents two cases, access denied and posts scheduled without media (5). No API or MCP changelog. The only changelog in the help centre's llms.txt is the Looker Studio connector's (0). Help centre pages per the 2 October check, not re-read on 10 November because Metricool's terms bar automated extraction. Total 23.

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 Metricool API + MCP +15

Metricool API + MCP 45

Per the 1 October check, not re-read on 10 November. No x402 or other machine payment (0). Plan prices are public, with no per-call price (10). The Free plan includes the MCP for 1 brand without a card, and the terms (3 November 2026) still list the MCP on every plan including Free, though the REST API needs Advanced or Custom (20). A person has to sign up in a browser (0). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Security & auth Metricool API + MCP +8

Metricool API + MCP 48

Per the 1 and 2 October checks, not re-read on 10 November. REST takes one account token in the X-Mc-Auth header, not the query string, plus userId and blogId. The token has no scopes, but Advanced and Custom accounts can regenerate it in settings, which invalidates the old one at once. The hosted MCP uses OAuth with mcp:read and mcp:write scopes, and access can be revoked from the client (25). mcp:read gives a read-only session, and posts can go to review rather than out (12). Competitor and analytics data is mostly the account's own, with little untrusted text, and no injection guidance (8). No audit log found (0). The privacy policy names a DPO. No security.txt, disclosure route or certification found, and the terms' data processing section refers to Article 32 GDPR measures in a DPA annex, not a certification (3). Total 48.

X MCP 40

OAuth 2.0 authorisation code with PKCE, scopes and automatic token refresh, per the MCP page re-read on 4 November, and the xurl source sends code_challenge_method S256. Every documented configuration sends the token in an Authorization header. The 8 October reading of the OAuth metadata on api.x.com is struck, since api.x.com's robots.txt disallows every path for unnamed agents. Less 6 because xurl 1.3.4, still the newest release on 4 November, requests a fixed set of 24 scopes including tweet.write and dm.write with no flag to narrow them, and the bridge config holds the client secret in plain text (24 of 30). The app-only Bearer route is read-only per the docs. No confirmation step is documented for article_publish or for removing bookmarks, so approval rests with the MCP client (10 of 20). Posts, profiles and news text come from anyone on X, and the security section has no guidance on prompt injection (0 of 15). The Developer Console shows usage and spend live and /2/usage/tweets returns daily counts. No per-call log was found (6 of 15). The 8 October programme reading came from x.com's security.txt (expired, pointing to HackerOne), and x.com's robots.txt disallows every path for unnamed agents, so that reading is struck. The xurl repository has no SECURITY.md, OSV lists no advisory for xurl on 4 November, and no SOC 2 or ISO 27001 statement or disclosure page was found on docs.x.com. Struck evidence on a fixed line is 0 (0 of 20). 24+10+0+6+0 = 40.

Transparency & trust Metricool API + MCP +7

Metricool API + MCP 66

Closed service with published terms from METRICOOL SOFTWARE, S.L. of Madrid (NIF B87527115), updated 3 November 2026 (15). Per the 1 and 2 October checks, the privacy policy says all data sits on EU servers, gives statutory retention periods of 4 to 6 years and folds a DPA into the service terms, and a signed DPA is available on request, with deletion or return of data when the contract ends (22). No deprecation policy or dated API notices found. The terms promise 15 days' notice of price rises only (0). Section 16.2.6 of the terms names two sub-processors, Amazon Web Services EMEA SARL for hosting and STR Sistemas y Desarrollos en Internet, S.L. for server administration, promises 30 days' written notice of changes to the list, and allows processing outside the EEA only with the customer's prior written approval (20). Total 57.

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.

Score by category

CategoryWeightMetricool API + MCPX MCPEdge
Reliability16%1572X MCP +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2365X MCP +42
Agent ergonomics13%3945X MCP +6
Security & auth14%4840Metricool API + MCP +8
Payments & pricing10%4530Metricool API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%670X MCP +64
Transparency & trust7%6659Metricool API + MCP +7
Negative events≤15-20
TotalF 31.4/100C 54.3/100

Facts side by side

FactMetricool API + MCPX MCP
KindHTTP APIMCP server
VendorMetricoolX Corp.
Hosted endpointhttps://app.metricool.com/apihttps://api.x.com/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
x402nono
LicencenoneProprietary hosted server under the X Developer Agreement. The xurl bridge on GitHub and npm is MIT
Read-only variant documentednoyes
llms.txtyesyes
Last release2025-10-072026-09-29
Terms last updatedno date given2026-04-27
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone1.4k stars, 6k npm/wk
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

Metricool API + MCP

A hosted MCP server with OAuth and separate read and write scopes works on every plan, Free included, for analytics and scheduled posts. The REST API needs the Advanced plan ($67 a month), with no published rate limits, retry guidance or changelog, and the MCP repository the help centre calls public still asks for credentials.

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

Metricool API + MCP

  1. Connect the hosted MCP at https://ai.metricool.com/mcp with OAuth, and ask only for mcp:read when the job is reporting
  2. Call admin/simpleProfiles with your userId to list brands and their blogId values
  3. Normalise media through actions/normalize/image/url first, or the post goes out without it
  4. Give publicationDate a dateTime and an IANA timezone, in the future
  5. Back off on your own, since no rate limits or Retry-After are documented

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

X MCP scores 54.3 (C) on agent readiness against Metricool API + MCP's 31.4 (F), and leads in 4 of 7 scored categories. Metricool API + MCP leads on security & auth, payments & pricing and transparency & trust.

Do Metricool API + MCP and X MCP need an API key?

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

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

Yes. Metricool API + MCP has a hosted endpoint at https://app.metricool.com/api and X MCP at https://api.x.com/mcp.

Other comparisons with Metricool 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.