twitter-command-center vs TwittrAPI
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). 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-10-23. 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
| Marketplace |  twitter-command-center |  TwittrAPI |
|---|---|---|
| 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: 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
| Fact | twitter-command-center | TwittrAPI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.twittrapi.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 5 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aisa-one/twitter-command-center | github.com/twittrapi/twittrapi-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-12 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
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
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 .
TwittrAPI
Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.
How to run each
twitter-command-center As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install twitter-command-center@claude-communityTwittrAPI As a remote MCP server
claude mcp add --transport http twittrapi-mcp https://mcp.twittrapi.com/mcpRequires: 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.
Only TwittrAPI 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: TwittrAPI · 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.