Sports MCP Server
Related Servers
Alternatives to Sports MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude Desktop to The Odds API, giving Claude real-time access to sports odds, scores, and schedules across 80+ sports and leagues worldwide.-
- AlicenseBqualityBmaintenanceA unified MCP server that aggregates 32 sports API providers into a single service, providing 336 tools for scores, stats, odds, esports, and more across 70+ sports.14165184 npm41MIT
- FlicenseBqualityDmaintenanceMCP server that enables Claude Desktop to access real-time sports data including live scores, fixtures, standings, and NBA statistics using free APIs.10-
- AlicenseBqualityBmaintenanceAn MCP server that exposes sports-data APIs from multiple providers (AFL, Sportsbet, Entain, NRL) as interchangeable tools, enabling cross-provider odds and stats comparison.500161 PyPI34MIT

RapidOddsAPI MCPofficial
AlicenseAqualityCmaintenanceLive bookmaker odds from 100+ sportsbooks (AU, US, EU), arbitrage and value bet finders, live game results and player stats for AI assistants. Built on the official RapidOddsAPI Python SDK. Free tier available.5MIT- AlicenseAqualityCmaintenanceMCP server for the FootballStack football data API. Gives LLM clients and AI agents (Claude, Cursor) access to real football data — fixtures, standings, lineups, live events, shot-level xG with pitch coordinates, and model-derived fair odds.12MIT
TDQS
Scored across 28 tools
The two provider prefixes (odds_ and sm_) create overlapping functionality: odds_get_odds, odds_get_event_odds, sm_odds_prematch, and sm_odds_inplay all provide odds, while odds_get_scores and sm_livescores both give scores. Although descriptions mention the source API, agents may struggle to pick the right tool when multiple options serve the same purpose.
The odds_ tools follow a verb_noun pattern (get_sports, get_events, get_odds), but the sm_ tools use bare nouns (livescores, fixtures, leagues) without verbs. This split between two naming conventions within one server is inconsistent, and compound names like sm_team_squads and sm_expected_xg further deviate from a clear pattern.
With 28 tools, the server is heavy and exceeds the typical 25-tool threshold. While it integrates two major sports APIs, the high count increases selection overhead and includes overlapping endpoints that could be consolidated or parameterized.
The server covers a broad spectrum of sports data: odds (prematch, inplay, historical, props), scores, fixtures, standings, statistics, predictions, and more. Minor gaps exist, such as no unified search across both providers, but for the stated sports data domain the coverage is nearly complete.