io.github.kubeshop/testkube-mcp vs io.github.pedrot95dev/twitterapi
io.github.kubeshop/testkube-mcp is an MCP server published by kubeshop. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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-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
| Marketplace |  io.github.kubeshop/testkube-mcp |  io.github.pedrot95dev/twitterapi |
|---|---|---|
| Official MCP Registry | Listed Version: 2.14.0 Forks (GitHub): 180 Stars (GitHub): 1 669 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 |
| Docker MCP Catalog | Listed Version: sha256:43aa88f2d416 Forks (GitHub): 180 Pulls (Docker Hub): 33 640 Stars (Docker Hub): 0 Stars (GitHub): 1 669 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
| Fact | io.github.kubeshop/testkube-mcp | io.github.pedrot95dev/twitterapi |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 669 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 640 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 180 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@pedrot95dev/twitterapi.mcp) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 9, secrets among them: 1 | 4, secrets among them: 4 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/kubeshop/testkube | github.com/pedrot95dev/twitterapi.mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 28 h ago, requires a key | no 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
io.github.kubeshop/testkube-mcp
MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
io.github.pedrot95dev/twitterapi
Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets.
How to run each
io.github.kubeshop/testkube-mcp As a local MCP server: Docker image
claude mcp add --env "TK_ACCESS_TOKEN=<YOUR_TK_ACCESS_TOKEN>" --env "TK_ENV_ID=<YOUR_TK_ENV_ID>" --env "TK_ORG_ID=<YOUR_TK_ORG_ID>" --transport stdio testkube -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ENV_ID -e TK_ORG_ID mcp/testkubeRequires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)
io.github.pedrot95dev/twitterapi As a local MCP server: npm package
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.mcpRequires: 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 io.github.kubeshop/testkube-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.pedrot95dev/twitterapi publish no list of tools, so we do not compare tools.
Settings each asks for
Only io.github.kubeshop/testkube-mcp asks for
TK_ACCESS_TOKEN (secret)TK_CONTROL_PLANE_URLTK_DASHBOARD_URLTK_DEBUGTK_ENV_ID (secret)TK_MCP_SHTTP_HOSTTK_MCP_SHTTP_PORTTK_MCP_TRANSPORTTK_ORG_ID (secret)
Only io.github.pedrot95dev/twitterapi asks for
TWITTERAPI_IO_AUTH_TOKEN (secret)TWITTERAPI_IO_CT0 (secret)TWITTERAPI_IO_KEY (secret)TWITTERAPI_IO_PROXY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.kubeshop/testkube-mcp · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.