# Metricool API + MCP vs TwitterAPI.io MCP (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.md (~4,100 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.json · canonical https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: E 38.4, rank #1360 of 1510 · https://www.anchorterminal.com/tools/metricool.min.md
- TwitterAPI.io MCP: D 49.3, rank #1101 of 1510 · https://www.anchorterminal.com/tools/twitterapi-io-mcp.min.md
- Metricool API + MCP, 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.
- TwitterAPI.io MCP, 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.

| Category | Metricool API + MCP | TwitterAPI.io MCP |
| --- | --- | --- |
| Reliability (16%) | 35 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 56 | 62 |
| Agent ergonomics (13%) | 39 | 78 |
| Security & auth (14%) | 48 | 37 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 6 | 40 |
| Transparency & trust (7%) | 61 | 41 |

| Fact (where they differ) | 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 |
| Pricing | Freemium | pay-per-use |
| Tools exposed | none | 12 |
| Read-only variant documented | no | 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 |

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.)