Ext Ops Panel
Open dashboard
Comparison

twitter-command-center vs TwitterAPIs

twitter-command-center is a plugin bundle for AI coding tools published by aisa-one. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-15. 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
Marketplacetwitter-command-centerTwitterAPIs
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.1
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

twitter-command-center vs TwitterAPIs
Facttwitter-command-centerTwitterAPIs
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.twitterapis.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/aisa-one/twitter-command-centergithub.com/twitterapis/twitterapis-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 h 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

twitter-command-center

In its own words, on Claude Code: claude-plugins-community:

Full Twitter/X data access and posting from Claude Code. Read user profiles, timelines, mentions, followers, tweet search (Latest/Top), replies, quotes, trending topics, lists, communities, and Spaces. Post tweets via OAuth relay — no passwords, no cookies, no proxies. Powered by AIsa API with pay-per-use pricing .

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

twitter-command-center As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install twitter-command-center@claude-community

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.

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 twitter-command-center publish no settings it asks for, so we do not compare settings.

What it can do: twitter-command-center · What it can do: TwitterAPIs · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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