Ext Ops Panel
Open dashboard
Comparison

TwitterXAPI vs TwittrAPI

TwitterXAPI is an MCP server published by twitterxapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). TwittrAPI is an MCP server published by twittrapi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceTwitterXAPITwittrAPI
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.2.0
Downloads/month (npm): 563
Downloads/week (npm): 563
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

TwitterXAPI vs TwittrAPI
FactTwitterXAPITwittrAPI
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-19
Where it runs (differs)Remote server (twitterxapi.com/api/mcp)Remote server (mcp.twittrapi.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 5
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/twittrapi/twittrapi-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Status out of date: last check 41 h ago returned HTTP 401Status out of date: last check 2 days ago returned HTTP 405

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

TwitterXAPI

In its own words, on Official MCP Registry:

Public X profiles, posts, conversations, followers, search, lists, trends, and communities.

TwittrAPI

In its own words, on Official MCP Registry:

Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.

How to run each

TwitterXAPI As a remote MCP server

Claude Code
claude mcp add --transport http twitterxapi https://twitterxapi.com/api/mcp

TwittrAPI As a remote MCP server

Claude Code
claude mcp add --transport http twittrapi-mcp https://mcp.twittrapi.com/mcp

Requires: RAPIDAPI_KEY (secret), TWITTRAPI_API_KEY (secret), TWITTRAPI_X_CHAT_PASSCODE (secret), TWITTRAPI_X_COOKIE (secret), TWITTRAPI_X_PROXY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of TwitterXAPI publish no settings it asks for, so we do not compare settings.

What it can do: TwitterXAPI · What it can do: TwittrAPI · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built