The Odds API

@theoddsapi what are the current betting lines for tonight's NBA games?

Here are tonight's NBA matchups with odds from major sportsbooks: Lakers vs. Celtics (7:30 PM ET) — DraftKings has Lakers -3.5 at -110, over/under 225.5; FanDuel shows -3 at -108. Warriors vs. Nuggets (10 PM ET) — Consensus line sits at Nuggets -6, total 232. Heat vs. 76ers (7 PM ET) — Pick'em on most books, slight lean to Heat -1. All lines pulled from US-region bookmakers within the last 15 minutes.

This example combines Get Events and Get Odds to surface live betting markets. The MCP requires a valid API key with sufficient quota — free tiers typically cap at 500 requests/month. Odds refresh frequently; responses reflect a snapshot, not real-time streaming. Users should confirm their API plan covers the desired sport and region before relying on this for time-sensitive decisions.

@theoddsapi track the score for the Manchester United match and alert me when it finishes

I've queried the current score using Get Scores for soccer_epl (English Premier League). Manchester United is leading 2-1 in the 78th minute against Arsenal. However, The Odds API does not support push notifications or webhooks — I can only poll scores on demand. To monitor completion, you'd need to re-prompt me periodically (e.g., '@theoddsapi check that United score again') or set up a separate polling script outside this Space.

This example highlights a common limitation: the MCP is pull-based, not event-driven. Get Scores returns current and recently completed match data, but continuous monitoring requires repeated calls. Users should be aware of their API quota when polling frequently. The MCP works best for one-off score checks or post-game summaries, not live alerting workflows.

@theoddsapi compare the moneyline movement for tomorrow's MLB games and summarize which teams are seeing sharp money

I pulled odds from Get Odds for all upcoming MLB games and compared opening lines to current spreads. The Dodgers opened at -140 and have moved to -165 against the Padres — a 25-cent shift suggesting heavy favorite action. The Yankees line tightened from -120 to -110, indicating balanced two-way betting. The Astros saw reverse line movement: opened -130, now -115 despite 70% of public bets on Houston, which often signals sharp money on the underdog. This synthesis is illustrative; actual line movement depends on bookmaker feed timing and your API's historical data access.

This example pairs the MCP's odds retrieval with AI reasoning to identify betting trends. The Odds API does not natively track line history — you'd need to store snapshots over time or use a paid tier with historical endpoints. The AI can infer patterns from current vs. opening lines if both are returned, but true sharp-money detection requires external context. Best for exploratory analysis, not automated trading signals.

When this MCP helps a 6-person fantasy football group make smarter bets

A fantasy league group meets Sunday mornings to set lineups and side bets. One person shares their screen in Zoom, pulls live odds from The Odds API MCP, and the group compares spreads across three bookmakers before locking picks. The MCP's Get Odds and Get Scores tools surface real-time lines and injury-adjusted numbers faster than toggling browser tabs. This works if your group bets recreationally and wants a single source for odds comparison. If you're running a serious betting operation with custom models or need historical line movement, this MCP won't replace a dedicated analytics platform. For casual groups making 5-10 picks a week, it's the right call.

When a 3-person sports blog uses this MCP to write betting previews

A small sports blog publishes game previews twice a week. The writer uses The Odds API MCP to pull opening lines, participant rosters, and recent scores in one Switchy session, then drafts the preview without switching apps. The Get Events and Get Participants tools let them confirm team names and matchup details without manual lookups. This setup works if your content calendar is predictable and you're covering mainstream sports with consistent API coverage. If you're writing about niche leagues or need play-by-play data, the MCP's six tools won't cover it. For blogs publishing 8-12 previews a month, it cuts research time in half.

When a 2-person team uses this MCP to validate a betting app concept

A founder and a developer are prototyping a mobile app that aggregates odds for college basketball. They use The Odds API MCP in Switchy to test data quality and API response times before committing to a paid tier. The Get Sports and Get Event Odds tools let them simulate user flows and confirm bookmaker coverage without writing integration code. This works for early validation when you're still deciding if the API's region and market filters match your product vision. If you need sub-second latency or plan to scale past 500 requests a day, you'll outgrow the free tier fast. For pre-launch testing, it's the cheapest way to prove the concept.