Ext Ops Panel
Open dashboard
Comparison

TwitterAPIs vs tabii (TRT Streaming)

TwitterAPIs is an MCP server published by TwitterAPIs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). tabii (TRT Streaming) is an MCP server published by mohammad-abbasi-sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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
MarketplaceTwitterAPIstabii (TRT Streaming)
Official MCP Registry Listed
Version: 0.28.1
Downloads/month (npm): 3 443
Downloads/week (npm): 200
Forks (GitHub): 3
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.28.1
Downloads/month (npm): 3 443
Downloads/week (npm): 200
Forks (GitHub): 3
Stars (GitHub): 6
Not marked · First seen
Not listed

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

TwitterAPIs vs tabii (TRT Streaming)
FactTwitterAPIstabii (TRT Streaming)
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)6 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last release (differs)2026-11-09Not published
Where it runs (differs)Remote server or your machineOn your machine (tabii-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/twitterapis/twitterapis-mcpgithub.com/mohammad-abbasi-sh/tabii-mcp
Changes in the last 7 days (differs)32
First seen (differs)2026-10-112026-11-11
Endpoint at the last check (differs)Responded 12 h ago, requires authenticationno 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

TwitterAPIs

In its own words, on Official MCP Registry:

Official MCP server for twitterapis.com. Twitter/X search, users, DMs, Grok, monitoring and writes.

tabii (TRT Streaming)

In its own words, on Official MCP Registry:

Unofficial read-only MCP server for tabii.com — TRT streaming catalog, live channels, people.

How to run each

TwitterAPIs As a remote MCP server

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

Requires: TWITTERAPIS_KEY (secret)

tabii (TRT Streaming) As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio tabii-mcp -- uvx tabii-mcp

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

Only TwitterAPIs 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 tabii (TRT Streaming) publish no settings it asks for, so we do not compare settings.

What it can do: TwitterAPIs · What it can do: tabii (TRT Streaming) · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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