Sportsdata MCP vs Rundida MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sportsdata MCP vs Rundida MCP
In-depth architectural comparison of the Sportsdata MCP and Rundida MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Sportsdata MCP
Sports · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Rundida MCP
Sports · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Sportsdata MCP if you need specialized Sports tools running via a local process. Choose Rundida MCP if your workspace requires Sports integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Sportsdata MCP when:
You need dedicated capabilities in the Sports domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Live sports data and cross-book betting odds as 500 tools across 28 providers — 10+ bookmakers (Sportsbet, TAB, Betfair, Pinnacle, FanDuel…), official league feeds (NBA, MLB, EPL, AFL, NRL, F1 telemetry), racing, and Kalshi/Polymarket prediction markets. Zero-config setup, no API keys for most providers. MIT.
86 running calculators, 29 marathon events, pace/time/distance calculations, race time predictions (Riegel formula), and heart rate training zones (Karvonen method) for AI agents. No API key required.
Category & Scope
Tools & Capabilities Breakdown
Sportsdata MCP Tools (829)
list_available_groups
List every tool group across all providers, which are currently enabled,
and each provider's auth requirements (env-var names + required/optional).
On a fresh install (no groups enabled) this is the only functional tool, so
the model can guide the user to enable what they want in sportsdata-mcp.yaml.
list_tools_by_capability
Discover tools by capability — the unit of cross-provider comparison.
Given a slug like 'sport.event_markets', returns every enabled tool exposing
it across providers. Pass no argument for the full capability → tools map.
afl_competitions_list
List all AFL competitions (AFL, AFLW, VFL, SANFL, …).
Returns: {meta:{pagination}, competitions:[{id, providerId, code, name}]}
Example: All 16 competitions
{"pageSize": 50}
Auth: none needed.
afl_competition_get
Get a single competition by integer id.
Returns: {meta, competitions:[{id, providerId, code, name}]}
Auth: none needed.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Sportsdata MCP is categorized under Sports and uses a local stdio subprocess. In contrast, Rundida MCP belongs to Sports using local stdio subprocess. Select Sportsdata MCP when you need capabilities focused on sports and Rundida MCP when you require tools for sports.
List comp seasons across all competitions (2012–present).
Returns: {meta:{pagination}, compSeasons:[{id, providerId, name, competition, season}]}
Auth: none needed.
afl_competition_compseasons
List comp seasons within one competition.
Returns: {meta, compSeasons:[...]}
Auth: none needed.
afl_compseason_get
Get a single comp season (embeds its full rounds array + currentRoundNumber).
Returns: {meta, compSeasons:[{id, providerId, name, shortName, season, rounds:[...], currentRoundNumber}]}
Auth: none needed.
afl_rounds_list
List rounds for a comp season (incl. byes, start/end times).
Returns: {rounds:[{id, providerId, roundNumber, abbreviation, byes, utcStartTime, utcEndTime}]}
Auth: none needed.
afl_ladders_get
Competition ladder up to a comp season's current round.
Returns: {compSeason, round, ladders:[{entries:[{position, team, played, thisSeasonRecord}]}]}
Example: 2026 AFL ladder
{"compSeasonId": 85}
Auth: none needed.
afl_seasons_list
List calendar-year season records.
Returns: {meta, seasons:[{id, year}]}
Auth: none needed.
afl_season_get
Get a single calendar-year season by id.
Returns: {meta, seasons:[{id, year}]}
Auth: none needed.