Sports MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODDS_API_KEY | Yes | Your Odds API key | |
| MCP_AUTH_TOKEN | No | Optional auth token to protect the HTTP server | |
| SPORTMONKS_TOKEN | Yes | Your SportMonks API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| odds_get_sportsA | List all available sports from The Odds API. Returns sport keys used in other endpoints. Free — no quota cost. |
| odds_get_eventsA | List upcoming and live events for a sport. Returns event IDs, teams, and commence times. Free — no quota cost. Use sport keys from odds_get_sports. |
| odds_get_oddsA | Get upcoming and live game odds for a sport. Returns bookmaker odds for specified markets and regions. This is the primary endpoint for pre-game odds analysis. Cost = markets × regions. |
| odds_get_scoresA | Get live scores and recently completed game scores. Live scores update ~every 30s. Use daysFrom (1-3) to include completed games. Cost: 1 without daysFrom, 2 with daysFrom. |
| odds_get_event_oddsA | Get odds for a SINGLE event with any available market (including player props, alternate lines, period markets). Use odds_get_events to find event IDs first. Cost = unique markets returned × regions. |
| odds_get_event_marketsA | Discover which market keys are available for a specific event from each bookmaker. Use this before odds_get_event_odds to know which markets to request. Cost: 1 quota. |
| odds_get_participantsA | List teams/players for a sport (whitelist of known participants). Cost: 1 quota. |
| odds_get_historical_oddsA | Get a snapshot of odds at a specific historical timestamp (available from June 2020, 5-min intervals from Sep 2022). Cost: 10 × markets × regions. PAID PLANS ONLY. |
| odds_get_historical_eventsA | List events as they appeared at a historical timestamp. Use to find event IDs for historical event odds. Cost: 1 quota. PAID PLANS ONLY. |
| odds_get_historical_event_oddsA | Get historical odds for a SINGLE event at a specific timestamp. Supports all markets including player props (available after 2023-05-03). Cost: 10 × markets × regions. PAID PLANS ONLY. |
| sm_livescoresA | Get live football/soccer scores. Modes: 'inplay' (currently playing), 'all' (today's livescores), 'latest' (most recently updated). Use include param for enriched data. |
| sm_fixturesA | Get football fixtures. Supports: by ID, by date, by date range, by date range for team, head-to-head, search by name. The core endpoint for match data. |
| sm_leaguesA | Get football leagues. Modes: 'all', 'by_id', 'live' (leagues currently in play), 'by_country', 'by_team', 'search'. Returns league IDs needed for other endpoints. |
| sm_seasonsA | Get football seasons. Modes: 'all', 'by_id', 'by_team', 'search'. Season IDs are needed for standings, statistics, and topscorers. |
| sm_standingsA | Get league standings / tables. Modes: 'by_season', 'by_round', 'live' (live standings by league). Essential for form analysis. |
| sm_teamsB | Get football teams. Modes: 'by_id', 'by_country', 'by_season', 'search'. Returns team IDs used across all endpoints. |
| sm_playersC | Get football players. Modes: 'by_id', 'by_country', 'search'. Rich data with includes. |
| sm_team_squadsA | Get a team's current squad or squad for a specific season. |
| sm_statisticsB | Get season/stage/round statistics for a participant (team or player). Essential for form and performance analysis. |
| sm_topscorersA | Get top scorers for a season or stage. |
| sm_predictionsB | Get SportMonks predictions. Modes: 'probabilities' (all), 'by_fixture' (fixture-specific probabilities), 'value_bets', 'value_bets_by_fixture'. Great for model cross-reference. |
| sm_expected_xgB | Get Expected Goals (xG) data by team or player. Requires xG add-on plan. |
| sm_odds_prematchA | Get pre-match odds from SportMonks. Modes: 'by_fixture', 'by_fixture_bookmaker', 'by_fixture_market', 'latest'. Useful for comparing with The Odds API data. |
| sm_odds_inplayB | Get live in-play odds from SportMonks. Modes: 'all', 'by_fixture', 'by_fixture_bookmaker', 'by_fixture_market', 'latest'. |
| sm_schedulesB | Get match schedules. Modes: 'by_season', 'by_team', 'by_season_team'. Useful for planning which fixtures to track. |
| sm_roundsB | Get round information. Modes: 'by_season', 'by_id'. Round IDs are needed for standings by round. |
| sm_marketsA | List available betting markets in SportMonks. Use market IDs with sm_odds_prematch and sm_odds_inplay. |
| sm_bookmakersB | List available bookmakers in SportMonks. Use bookmaker IDs with odds endpoints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.