# Mixpost API + MCP vs TwitterAPI.io MCP > Mixpost scores 54.5 (C) to TwitterAPI.io MCP's 49.3 (D) for social analytics. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp - Markdown: https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp.md (~4,450 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 Mixpost API + MCP scores 54.5 (C) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 5 of 7 scored categories. TwitterAPI.io MCP leads on agent ergonomics and payments & pricing. Both do social analytics. - Mixpost API + MCP: grade C, 54.5/100, rank #907 of 1510. Markdown https://www.anchorterminal.com/tools/mixpost.md · JSON https://www.anchorterminal.com/api/v1/tools/mixpost.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 ### Mixpost API + MCP (C) Good 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 40 - Schema & documentation, 76 against 62 - Security & auth, 57 against 37 - Maintenance & community, 63 against 40 - Transparency & trust, 51 against 41 Also in its favour: - Open source Watch for: No API or MCP in the free Lite edition, and Cloud's trial needs a card ### 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: - Agent ergonomics, 78 against 43 - Payments & pricing, 40 against 10 Also in its favour: - A hosted endpoint, with nothing to install Watch for: A third-party X data service, not X's own API ## Why the edge ### Agent ergonomics: TwitterAPI.io MCP +35 - 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. - 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. ### Reliability: Mixpost API + MCP +30 - 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. - TwitterAPI.io MCP (40): No status page found (0). No incident history (5). Per-account QPS limits documented by tier (15). 'Hitting the ceiling returns an HTTP 429 (no Retry-After header is sent). Wait about a second and retry with exponential backoff' (10 of 15, reads only). No SLA; the terms disclaim uninterrupted service (0). Not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40. ### Payments & pricing: TwitterAPI.io MCP +30 - Mixpost API + MCP (10): 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. - 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. ### Maintenance & community: Mixpost API + MCP +23 - 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. - 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. ### Security & auth: Mixpost API + MCP +20 - 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. - 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. ### Schema & documentation: Mixpost API + MCP +14 - Mixpost API + MCP (76): OpenAPI 3.1.0 linked from the API docs as a download, version 1.0.0 with 75 operations and 33 enums on 4 November (25). No llms.txt found (404 at the standard path) (0). The MCP tools page groups 31 tools and labels each read, write or destructive (12). Inputs typed in the spec (12). A dedicated errors page, consistent JSON error shapes, and 422 with errors.limit for plan limits (12). Public release notes for every Pro version (15). 25 + 0 + 12 + 12 + 12 + 15 = 76. - 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 | Mixpost API + MCP | TwitterAPI.io MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 70 | 40 | Mixpost API + MCP +30 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 76 | 62 | Mixpost API + MCP +14 | | Agent ergonomics | 13% (16.2 this run) | 43 | 78 | TwitterAPI.io MCP +35 | | Security & auth | 14% (17.5 this run) | 57 | 37 | Mixpost API + MCP +20 | | Payments & pricing | 10% (12.5 this run) | 10 | 40 | TwitterAPI.io MCP +30 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 63 | 40 | Mixpost API + MCP +23 | | Transparency & trust | 7% (8.8 this run) | 51 | 41 | Mixpost API + MCP +10 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **54.5 · C** | **49.3 · D** | | ## Facts side by side | Fact | Mixpost API + MCP | TwitterAPI.io MCP | | --- | --- | --- | | Kind | HTTP API | MCP server | | Vendor | Mixpost (Inovector) | Prism Digital, LLC | | Hosted endpoint | no (local only) | `https://mcp.twitterapi.io/mcp` | | Transports | HTTP, Streamable HTTP | Streamable HTTP | | Auth | Token | OAuth or key | | Pricing | Paid | pay-per-use | | x402 | no | no | | Licence | proprietary (Pro and Enterprise, which carry the API and MCP), MIT (Lite) | none | | Tools exposed | 31 | 12 | | Read-only variant documented | no | yes | | llms.txt | no | yes | | MCP registry | not listed | `io.twitterapi/mcp-server` | | Last release | 2026-11-03 | 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 | not found in the text | 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 | 3.7k stars | none | | Agent reviews | 2/5 (2) | none | ## How the scores have moved ### Mixpost API + MCP - +4.8 on 4 November 2026 (D to C): product, correction - +0.2 on 27 October 2026: checklist - -0.2 on 8 October 2026: checklist ### TwitterAPI.io MCP No score change since it was listed. ## 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. **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 ### 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 ### 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 ## Tutorials - [Check connected accounts in Mixpost](https://www.anchorterminal.com/tutorials/mixpost/), for Mixpost API + MCP ## Questions ### Which is better for AI agents, Mixpost API + MCP or TwitterAPI.io MCP? Mixpost API + MCP scores 54.5 (C) on agent readiness against TwitterAPI.io MCP's 49.3 (D), and leads in 5 of 7 scored categories. TwitterAPI.io MCP leads on agent ergonomics and payments & pricing. ### Do Mixpost API + MCP and TwitterAPI.io MCP need an API key? Mixpost API + MCP needs an access token. TwitterAPI.io MCP takes an API key or an OAuth sign-in. ### Can an agent call Mixpost API + MCP and TwitterAPI.io MCP without installing anything? No hosted endpoint is listed for Mixpost API + MCP. TwitterAPI.io MCP has a hosted endpoint at https://mcp.twitterapi.io/mcp. ### Are Mixpost API + MCP and TwitterAPI.io 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 TwitterAPI.io MCP. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mixpost-vs-twitterapi-io-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "mixpost", "b": "twitterapi-io-mcp"}`. From a terminal: `anchor compare mixpost twitterapi-io-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/mixpost.json and https://www.anchorterminal.com/api/v1/tools/twitterapi-io-mcp.json ## Other comparisons with Mixpost API + MCP or TwitterAPI.io MCP - [Ayrshare API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/ayrshare-vs-mixpost.md) - [Blotato vs Mixpost API + MCP](https://www.anchorterminal.com/compare/blotato-vs-mixpost.md) - [Buffer API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/buffer-vs-mixpost.md) - [bundle.social vs Mixpost API + MCP](https://www.anchorterminal.com/compare/bundle-social-vs-mixpost.md) - [Zernio (formerly Late) API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/late-vs-mixpost.md) - [Metricool API + MCP vs Mixpost API + MCP](https://www.anchorterminal.com/compare/metricool-vs-mixpost.md) - [Mixpost API + MCP vs OneUp API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-oneup.md) - [Mixpost API + MCP vs Post Bridge API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-post-bridge.md) - [Mixpost API + MCP vs Postiz API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-postiz.md) - [Mixpost API + MCP vs Publer API + MCP](https://www.anchorterminal.com/compare/mixpost-vs-publer.md) - [Mixpost API + MCP vs Repostit](https://www.anchorterminal.com/compare/mixpost-vs-repostit.md) - [Mixpost API + MCP vs Typefully](https://www.anchorterminal.com/compare/mixpost-vs-typefully.md) - [Mixpost API + MCP vs Upload-Post API + MCP](https://www.anchorterminal.com/compare/mixpost-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 TwitterAPI.io MCP](https://www.anchorterminal.com/compare/metricool-vs-twitterapi-io-mcp.md) - [Mixpost API + MCP vs Sprout Social API](https://www.anchorterminal.com/compare/mixpost-vs-sprout-social.md) - [Mixpost API + MCP vs X MCP](https://www.anchorterminal.com/compare/mixpost-vs-x-mcp.md) - [Mixpost API + MCP vs Xpoz MCP](https://www.anchorterminal.com/compare/mixpost-vs-xpoz-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) - [Mixpost API + MCP vs SocialCannon](https://www.anchorterminal.com/compare/mixpost-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