Ext Ops Panel
Open dashboard
Comparison

com.jojapi/x-twitter vs io.github.pedrot95dev/twitterapi

com.jojapi/x-twitter is an MCP server published by jojapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pedrot95dev/twitterapi is an MCP server published by pedrot95dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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/x-twitterio.github.pedrot95dev/twitterapi
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 119
Downloads/week (npm): 14
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

com.jojapi/x-twitter vs io.github.pedrot95dev/twitterapi
Factcom.jojapi/x-twitterio.github.pedrot95dev/twitterapi
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.jojapi.com/x)On your machine (@pedrot95dev/twitterapi.mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 4
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/pedrot95dev/twitterapi.mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 11 h agono remote endpoint we check

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/x-twitter

In its own words, on Official MCP Registry:

X (twitter): x, xapi, Twitter, twitter api, twitters ,tweets, tw, twttr, FollowerIds, friendsIds.

io.github.pedrot95dev/twitterapi

In its own words, on Official MCP Registry:

Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets.

How to run each

com.jojapi/x-twitter As a remote MCP server

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

io.github.pedrot95dev/twitterapi As a local MCP server: npm package

Claude Code
claude mcp add --env "TWITTERAPI_IO_AUTH_TOKEN=<YOUR_TWITTERAPI_IO_AUTH_TOKEN>" --env "TWITTERAPI_IO_CT0=<YOUR_TWITTERAPI_IO_CT0>" --env "TWITTERAPI_IO_KEY=<YOUR_TWITTERAPI_IO_KEY>" --env "TWITTERAPI_IO_PROXY=<YOUR_TWITTERAPI_IO_PROXY>" --transport stdio twitterapi -- npx -y @pedrot95dev/twitterapi.mcp

Requires: TWITTERAPI_IO_AUTH_TOKEN (secret), TWITTERAPI_IO_CT0 (secret), TWITTERAPI_IO_KEY (secret), TWITTERAPI_IO_PROXY (secret)

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

Only com.jojapi/x-twitter has a remote endpoint we 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/x-twitter publish no settings it asks for, so we do not compare settings.

What it can do: com.jojapi/x-twitter · What it can do: io.github.pedrot95dev/twitterapi · 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