arenamcp vs PokerData
arenamcp is an MCP server published by josharmour. Marketplaces we read that list it: 1 (PyPI (MCP servers)). PokerData is an MCP server published by hft-studio. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  arenamcp |   PokerData |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 4.0.54 Downloads/month (PyPI): 76 Downloads/week (PyPI): 194 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.4 Downloads/month (npm): 995 Downloads/week (npm): 838 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.4 Downloads/month (npm): 995 Downloads/week (npm): 838 Forks (GitHub): 0 Stars (GitHub): 2 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 | arenamcp | PokerData |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 10 (better) | 2 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-09 (better) | 2026-10-17 (worse) |
| Where it runs (differs) | On your machine (arenamcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/josharmour/mtgacoach | github.com/hft-studio/pokerdata-mcp |
| Changes in the last 7 days (differs) | 3 | 1 |
| First seen (differs) | 2026-10-12 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 h 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
arenamcp
AI-powered real-time coaching and autopilot for Magic: The Gathering Arena
PokerData
GTO poker solver data: NLHE/PLO preflop ranges, postflop strategy, EV. 6-max NL preflop free.
How to run each
arenamcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PokerData As a remote MCP server
claude mcp add --transport http pokerdata https://pokerdata.io/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: POKERDATA_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only PokerData 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 arenamcp publish no settings it asks for, so we do not compare settings.
What it can do: arenamcp · What it can do: PokerData · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.