Ext Ops Panel
Open dashboard
Comparison

com.jojapi/twitter vs TwitterAPIs

com.jojapi/twitter is an MCP server published by jojapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). TwitterAPIs is an MCP server published by TwitterAPIs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacecom.jojapi/twitterTwitterAPIs
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.23.0
Downloads/month (npm): 4 365
Downloads/week (npm): 125
Forks (GitHub): 1
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

com.jojapi/twitter vs TwitterAPIs
Factcom.jojapi/twitterTwitterAPIs
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub1
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (mcp.jojapi.com/twitter)Remote server (api.twitterapis.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/twitterapis/twitterapis-mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agoResponded 2 days ago, requires a key

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

com.jojapi/twitter

In its own words, on Official MCP Registry:

X (formerly Twitter): X (formerly Twitter) public and private data API for search, posts (Tweets).

TwitterAPIs

In its own words, on Official MCP Registry:

Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.

How to run each

com.jojapi/twitter As a remote MCP server

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

TwitterAPIs As a remote MCP server

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

Requires: TWITTERAPIS_KEY (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 com.jojapi/twitter publish no settings it asks for, so we do not compare settings.

What it can do: com.jojapi/twitter · What it can do: TwitterAPIs · 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