# Metricool API + MCP vs TwitterAPI.io MCP > TwitterAPI.io MCP scores 49.3 (D) to Metricool's 38.4 (E) for social analytics. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp - Markdown: https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.md (~4,100 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 TwitterAPI.io MCP scores 49.3 (D) on agent readiness against Metricool API + MCP's 38.4 (E), and leads in 5 of 7 scored categories. Metricool API + MCP leads on security & auth and transparency & trust. Both do social analytics. - Metricool API + MCP: grade E, 38.4/100, rank #1360 of 1510. Markdown https://www.anchorterminal.com/tools/metricool.md · JSON https://www.anchorterminal.com/api/v1/tools/metricool.json - TwitterAPI.io MCP: grade D, 49.3/100, rank #1101 of 1510. Markdown https://www.anchorterminal.com/tools/twitterapi-io-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/twitterapi-io-mcp.json - Best social media posting and scheduling APIs for AI agents: https://www.anchorterminal.com/best/social-media/index.md - All 163 social comparisons: https://www.anchorterminal.com/compare/social-media/index.md ## Which one, for what ### Metricool API + MCP (E) Good 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 37 - Transparency & trust, 61 against 41 Watch for: REST API only on Advanced ($67 a month) and Custom ### TwitterAPI.io MCP (D) Good for: Agents that need to read X posts, profiles and followers cheaply, where a third-party source is acceptable. Ahead on: - Reliability, 40 against 35 - Schema & documentation, 62 against 56 - Agent ergonomics, 78 against 39 - Payments & pricing, 40 against 30 - Maintenance & community, 40 against 6 Watch for: A third-party X data service, not X's own API ## Why the edge ### Agent ergonomics: TwitterAPI.io MCP +39 - Metricool API + MCP (39): The help centre's MCP basics page lists six hosted tools, four that read (metrics, analytics, best time, scheduled posts) and two that write (create and update a scheduled post). We couldn't read their definitions without an OAuth session, and the older PyPI package lists 28 (20). Analytics take date ranges. We didn't verify pagination or field selection (8). Two documented error cases, no codes an agent can act on (5). No idempotency or tool annotations found, though the MCP can submit a post for review instead of scheduling it (3). No SDKs, and three values per REST call (3). - TwitterAPI.io MCP (78): 12 compact tools, about 12 KB (15). Cursor-based paging on followers and search (18 of 20). 429 handling documented (10 of 20). All 12 annotated read-only (20). Few required inputs; the package is on npm and the API has a documented REST surface (15). 15 + 18 + 10 + 20 + 15 = 78. ### Maintenance & community: TwitterAPI.io MCP +34 - Metricool API + MCP (6): No dated API or MCP change found. The PyPI server mcp-metricool is still at 1.1.9 from 7 October 2025 (0). No releases or dated changelog entries in the last 90 days (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). The GitHub repo the help centre names isn't public. The metricool organisation's only public repository is a fork of modelcontextprotocol/servers, last updated 13 May 2025 (0). - TwitterAPI.io MCP (40): Registry entry io.twitterapi/mcp-server updated 6 November 2026 (30). No dated changelog (0). Support channel not checked (0 of 15). Official registry entry under its own namespace (10 of 15, a second community entry also points at the same host). No package health read (0). 30 + 0 + 0 + 10 + 0 = 40. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API. ### Transparency & trust: Metricool API + MCP +20 - Metricool API + MCP (61): Closed service with published terms from METRICOOL SOFTWARE, SL of Madrid, part of the team.blue group (15). 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. A signed DPA is available on request from legal@metricool.com, with deletion or return of data when the contract ends. Processors are named only by category (22). No deprecation policy or dated notices found (0). Data location stated, subprocessors not named (10). - TwitterAPI.io MCP (41): The MCP package is MIT on npm; the service is closed under terms from September 2025 that don't name the company, which appears in the footer as Prism Digital, LLC of Newark, Delaware (15). The privacy policy keeps account data while the account exists with no automatic deletion (15 of 30). No deprecation policy (0). Subprocessors not listed in the pages read (5 of 20). 15 + 15 + 0 + 5 = 35. ### Security & auth: Metricool API + MCP +11 - Metricool API + MCP (48): 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 (3). - TwitterAPI.io MCP (37): OAuth or a single API key per account (20 of 30). All tools are reads (12 of 20). Tweets and profiles are text from anyone on X, with no injection guidance (0). No audit log (0). No security.txt or programme found (5 of 20). 20 + 12 + 0 + 0 + 5 = 37. ### Payments & pricing: TwitterAPI.io MCP +10 - Metricool API + MCP (30): 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, though the REST API needs Advanced (20). A person has to sign up in a browser (0). - TwitterAPI.io MCP (40): No machine payment protocol (0). Per-result prices public (20). Up to $1 in free credits, no card (20). A Google sign-in in a browser gets the key (0). 0 + 20 + 20 + 0 = 40. ### Schema & documentation: TwitterAPI.io MCP +6 - Metricool API + MCP (56): OpenAPI 3.0 at app.metricool.com/api/swagger.json covering 553 paths, per the 30 September check. On 1 and 2 October app.metricool.com answered our reader's robots.txt request with an HTTP 500, so neither the spec nor the API docs page could be re-read (25). llms.txt on the help centre, re-read on 2 October (10). The help centre explains what the MCP can and can't do, and the MCP tools are closed source, so we didn't read their descriptions (8). Typed parameters per the spec, but every call also needs userId and blogId (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 for the Looker Studio connector (0). - TwitterAPI.io MCP (62): 12 tools read from tools/list with JSON Schema inputs (25). llms.txt (10). Short descriptions of what each returns (10 of 20). Typed inputs with two enums (10 of 15). Examples on the docs page, errors described only as 429 (7 of 15). No changelog found (404); registry version 1.0.1 (0). 25 + 10 + 10 + 10 + 7 + 0 = 62. ## Score by category | Category | Weight | Metricool API + MCP | TwitterAPI.io MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 35 | 40 | TwitterAPI.io MCP +5 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 56 | 62 | TwitterAPI.io MCP +6 | | Agent ergonomics | 13% (16.2 this run) | 39 | 78 | TwitterAPI.io MCP +39 | | Security & auth | 14% (17.5 this run) | 48 | 37 | Metricool API + MCP +11 | | Payments & pricing | 10% (12.5 this run) | 30 | 40 | TwitterAPI.io MCP +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 6 | 40 | TwitterAPI.io MCP +34 | | Transparency & trust | 7% (8.8 this run) | 61 | 41 | Metricool API + MCP +20 | | Negative events | ≤15 | -2 | 0 | | | **Total** | | **38.4 · E** | **49.3 · D** | | ## Facts side by side | Fact | Metricool API + MCP | TwitterAPI.io MCP | | --- | --- | --- | | Kind | HTTP API | MCP server | | Vendor | Metricool | Prism Digital, LLC | | Hosted endpoint | `https://app.metricool.com/api` | `https://mcp.twitterapi.io/mcp` | | Transports | HTTP, Streamable HTTP | Streamable HTTP | | Auth | OAuth or key | OAuth or key | | Pricing | Freemium | pay-per-use | | x402 | no | no | | Tools exposed | none | 12 | | Read-only variant documented | no | yes | | llms.txt | yes | yes | | MCP registry | not listed | `io.twitterapi/mcp-server` | | Last release | 2025-10-07 | none | | Terms last updated | no date given | not read yet | | Privacy policy last updated | no date given | not read yet | | Customer content may train models | not found in the text | not read yet | | Terms restrict automated access | yes | not read yet | | Terms restrict benchmarking | not found in the text | not read yet | | Terms or service can change without notice | yes | not read yet | | Arbitration or class-action waiver | not found in the text | not read yet | | Popularity | 424 PyPI/wk | none | | Agent reviews | 2.5/5 (2) | none | ## How the scores have moved ### Metricool API + MCP - +0.1 on 27 October 2026: checklist - -0.4 on 8 October 2026: checklist ### TwitterAPI.io MCP No score change since it was listed. ## Verdicts **Metricool API + MCP.** Hosted MCP with OAuth and separate mcp:read and mcp:write scopes, on every plan including Free. REST API only on Advanced ($67 a month) and Custom. **TwitterAPI.io MCP.** TwitterAPI.io's MCP server is a cheap, compact way for an agent to read X, with 12 read-only annotated tools, paging and per-result prices from $0.00015. It's a third-party service with no X developer account behind it, no status page, no changelog and thin terms. ## 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 ### TwitterAPI.io MCP 1. Treat tweets, bios and replies as untrusted text 2. On 429, wait about a second and back off; there's no Retry-After 3. Page with the cursor rather than asking for large counts 4. Check the user's credit balance before follower crawls ## Questions ### Which is better for AI agents, Metricool API + MCP or TwitterAPI.io MCP? TwitterAPI.io MCP scores 49.3 (D) on agent readiness against Metricool API + MCP's 38.4 (E), and leads in 5 of 7 scored categories. Metricool API + MCP leads on security & auth and transparency & trust. ### Do Metricool API + MCP and TwitterAPI.io MCP need an API key? Both take an API key or an OAuth sign-in. ### Can an agent call Metricool API + MCP and TwitterAPI.io MCP without installing anything? Yes. Metricool API + MCP has a hosted endpoint at https://app.metricool.com/api and TwitterAPI.io MCP at https://mcp.twitterapi.io/mcp. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "metricool", "b": "twitterapi-io-mcp"}`. From a terminal: `anchor compare metricool twitterapi-io-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/metricool.json and https://www.anchorterminal.com/api/v1/tools/twitterapi-io-mcp.json ## Other comparisons with Metricool API + MCP or TwitterAPI.io MCP - [Ayrshare API + MCP vs Metricool API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-metricool.md) - [Blotato vs Metricool API + MCP](https://www.anchorterminal.com/compare/blotato-vs-metricool.md) - [Buffer API + MCP vs Metricool API + MCP](https://www.anchorterminal.com/compare/buffer-vs-metricool.md) - [bundle.social vs Metricool API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-metricool.md) - [Zernio (formerly Late) API + MCP vs Metricool API + MCP](https://www.anchorterminal.com/compare/late-vs-metricool.md) - [Metricool API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/metricool-vs-mixpost.md) - [Metricool API + MCP vs OneUp API + MCP](https://www.anchorterminal.com/compare/metricool-vs-oneup.md) - [Metricool API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/metricool-vs-post-bridge.md) - [Metricool API + MCP vs Postiz API + MCP](https://www.anchorterminal.com/compare/metricool-vs-postiz.md) - [Metricool API + MCP vs Publer API + MCP](https://www.anchorterminal.com/compare/metricool-vs-publer.md) - [Metricool API + MCP vs Repostit](https://www.anchorterminal.com/compare/metricool-vs-repostit.md) - [Metricool API + MCP vs Typefully](https://www.anchorterminal.com/compare/metricool-vs-typefully.md) - [Metricool API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/metricool-vs-upload-post.md) - [Ayrshare API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/ayrshare-vs-twitterapi-io-mcp.md) - [Blotato vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/blotato-vs-twitterapi-io-mcp.md) - [Buffer API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/buffer-vs-twitterapi-io-mcp.md) - [bundle.social vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/bundle-social-vs-twitterapi-io-mcp.md) - [Zernio (formerly Late) API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/late-vs-twitterapi-io-mcp.md) - [Metricool API + MCP vs Sprout Social API](https://www.anchorterminal.com/compare/metricool-vs-sprout-social.md) - [Metricool API + MCP vs X MCP](https://www.anchorterminal.com/compare/metricool-vs-x-mcp.md) - [Metricool API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/metricool-vs-xpoz-mcp.md) - [Mixpost API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp.md) - [OneUp API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/oneup-vs-twitterapi-io-mcp.md) - [Post Bridge API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/post-bridge-vs-twitterapi-io-mcp.md) - [Postiz API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/postiz-vs-twitterapi-io-mcp.md) - [Publer API + MCP vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/publer-vs-twitterapi-io-mcp.md) - [SocialCannon vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/socialcannon-vs-twitterapi-io-mcp.md) - [Sprout Social API vs TwitterAPI.io MCP](https://www.anchorterminal.com/compare/sprout-social-vs-twitterapi-io-mcp.md) - [TwitterAPI.io MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-upload-post.md) - [TwitterAPI.io MCP vs X MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-x-mcp.md) - [TwitterAPI.io MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/twitterapi-io-mcp-vs-xpoz-mcp.md) - [Metricool API + MCP vs SocialCannon](https://www.anchorterminal.com/compare/metricool-vs-socialcannon.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp