Odds-API MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODDS_API_KEY | Yes | Your API key from odds-api.io |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sportsA | List all available sports with their name and slug identifier. |
| get_bookmakersA | List all supported bookmakers with their name and active status. |
| get_selected_bookmakersA | Get the authenticated user's currently selected bookmakers. |
| select_bookmakersC | Add bookmakers to the authenticated user's selection. |
| clear_selected_bookmakersA | Clear all selected bookmakers for the authenticated user. Limited to once every 12 hours. |
| get_marketsA | List the exact market names served for a sport, with how to read each one (shape), the period it covers and whether it is available prematch and live. Use it before passing markets to other tools; names must match in full, e.g. 'ML' not 'Match Winner'. |
| get_leaguesB | Get leagues for a sport. Returns league name, slug, and active event count. |
| get_eventsB | Get events for a sport with filtering by league, participant, status, date range, bookmaker availability, and pagination support. |
| get_eventA | Get a single event by its unique ID. |
| get_live_eventsA | Get all currently live events across all sports, optionally filtered by sport. |
| search_eventsA | Search events by team name or text query. Returns up to 10 matching results. |
| get_oddsC | Get betting odds for a specific event from selected bookmakers. |
| get_multi_oddsA | Get odds for multiple events in a single request (up to 10 events). Counts as only 1 API call. |
| get_odds_movementsA | Get historical odds line movements for an event from a bookmaker. Returns opening, latest, and all intermediate price changes for a specific market. |
| get_updated_oddsA | Get odds updated since a Unix timestamp for a bookmaker and sport, limited to the markets you name. The timestamp must be at most 90 seconds old. Useful for efficient polling. |
| get_dropping_oddsA | Get odds that have dropped the most from opening, based on sharp bookmaker data. Useful for tracking where sharp money is moving. Updated every ~10 seconds. Only available on paid plans. Response includes drop percentages for multiple time windows (sinceOpening, 12h, 24h, 48h). For player prop markets, the response includes market.label with the player name (e.g. 'Carlos Baleba'). Use markets=Player Props to get all player prop markets across all sports (football includes Anytime Goalscorer, Player Passes, Player Shots, Player Shots on Target, etc.). IMPORTANT: Always pass the sport parameter when the user mentions or implies a specific sport — the global (no-sport) endpoint is heavily dominated by player props and will return very few main market results. |
| get_historical_eventsA | Get finished events for a sport and league within a date range (max 31-day span). |
| get_historical_oddsB | Get closing odds and final scores for a finished event from selected bookmakers. |
| get_settlementsA | Get what happened in up to 50 events: status (pending, live, awaiting_result, settled, cancelled), final score by period and a |
| grade_betsA | Settle up to 50 bets. Each selection is graded as won, lost, void, half_won, half_lost, pending or ungradeable, with a reason, a |
| get_value_betsA | Get positive expected value betting opportunities for a bookmaker. Updated every 5 seconds. EV formula: (Probability x Odds) - 1. |
| get_arbitrage_betsA | Get arbitrage opportunities across bookmakers. Returns profit margin, optimal stake distribution, and direct bet links for each leg. |
| get_participantsA | Get teams/participants for a sport, optionally filtered by name search. |
| get_participantA | Get a single participant/team by their unique ID. |
| get_documentationA | Fetch the complete Odds-API.io API documentation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Odds-API.io Documentation | Complete API documentation for Odds-API.io |
| OpenAPI Specification | OpenAPI/Swagger specification for Odds-API.io |
TDQS
Scored across 25 tools
Tools are mostly distinct, but get_events/get_historical_events/get_live_events/search_events slightly overlap, and get_odds/get_updated_odds/get_multi_odds/get_odds_movements require inference to separate. Descriptions do clarify the boundaries, so misselection is unlikely but possible.
Every tool follows the same verb_noun snake_case pattern (get_, select_, clear_, grade_, search_), with no camelCase or stylistic deviations.
25 tools is at the heavy end for an odds API but each covers a distinct resource or analysis function; it is borderline rather than excessive.
The surface covers sports, leagues, events, odds, settlements, grading, and value/arbitrage betting, but lacks explicit market/league discovery tools and dedicated bookmaker removal, leaving minor gaps.