Lumify Sports Intelligence
This MCP server exposes read-only Lumify sports-intelligence tools for schedules, live scores, odds, betting splits, AI bet insights, and team/player lookup.
Discover sports, leagues, seasons, and current seasons.
List/filter events by sport, league, status, date range, team, season, or recommended bets; paginate and optionally include scores.
Search events with natural-language queries like “live nfl games today.”
Fetch single or batch event details, including participants/venue and optional odds/intelligence.
Get lightweight live score snapshots with status, period, clock, and period scores.
Get current odds per bookmaker and historical line movement.
Get public betting splits (bets%/handle%) and AI bet intelligence with confidence, signals, rationale, and narratives.
Look up teams and players, team/player profiles, and player schedules/results.
All tools are read-only, and optional odds/intelligence calls are credit-aware.
Provides access to real-time schedules, live scores, odds, line movement, public betting splits, and AI-powered confidence for FIFA World Cup and other soccer leagues.
Provides access to real-time schedules, live scores, odds, line movement, public betting splits, and AI-powered confidence for MLB games.
Provides access to real-time schedules, live scores, odds, line movement, public betting splits, and AI-powered confidence for NBA games.
Provides access to real-time schedules, live scores, odds, line movement, public betting splits, and AI-powered confidence for NHL games.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Lumify — Client SDKs & MCP
Official client libraries and Model Context Protocol (MCP) integration for Lumify, the agent-ready sports-intelligence API: real-time schedules, live scores, odds, line movement, public betting splits, and explainable AI bet confidence across MLB, NFL, NCAAF, NCAAB, NBA, NHL, tennis, and soccer (MLS, EPL, La Liga, Serie A, Bundesliga, Ligue 1, and UEFA Champions League).
This repository is the public home for the client SDKs, the MCP stdio bridge, and developer docs/examples. Lumify itself is a hosted API at
https://lumify.ai— you don't run a server yourself.
Get an API key
Everything here authenticates with a Lumify API key (lmfy-...).
Fastest — no signup: grab a free instant trial key at https://lumify.ai/docs/ai (click "Get instant trial key"). No account, email, or credit card — 100 credits, 14-day expiry. Paste it and start calling.
Persistent account: create a key at https://lumify.ai/api-keys — free trial with 1,000 credits, no credit card required.
export LUMIFY_API_KEY="lmfy-xxxxxx.yyyyyyyy"Related MCP server: PropLine
Packages
Runtime | Package | Install | Docs |
TypeScript / JavaScript |
| ||
Python |
| ||
LangChain |
| ||
LlamaIndex |
| ||
CrewAI |
| ||
MCP stdio bridge |
|
Quick start
TypeScript
import { Lumify } from "@lumifyai/sdk";
const client = new Lumify({ apiKey: process.env.LUMIFY_API_KEY! });
const { sports } = await client.sports.list();
const event = await client.events.get(12345, { includeOdds: true, includeIntelligence: true });
console.log(event.status, event.intelligence?.bets);Python
import os
from lumify import Lumify
client = Lumify(api_key=os.environ["LUMIFY_API_KEY"])
sports = client.sports.list()
event = client.events.get(12345, include_odds=True, include_intelligence=True)
print(event["status"], event.get("intelligence"))curl
curl https://lumify.ai/v1/events?sport=nfl&status=inprogress \
-H "Authorization: Bearer $LUMIFY_API_KEY"Use it from an AI agent (MCP)
Lumify runs a hosted MCP server at https://lumify.ai/mcp (Streamable HTTP,
JSON mode, stateless). Point any MCP-compatible client at it.
Remote (Cursor, VS Code, Claude Desktop with remote support):
{
"mcpServers": {
"lumify": {
"url": "https://lumify.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Local stdio (clients without remote MCP support):
{
"mcpServers": {
"lumify": {
"command": "npx",
"args": ["-y", "@lumifyai/mcp"],
"env": { "LUMIFY_API_KEY": "YOUR_API_KEY" }
}
}
}See the MCP bridge README and the MCP guide for the full tool catalog.
Examples
Demo | Path | Tutorial |
Live sports scoreboard |
cd examples/scoreboard
npm install && cp .env.example .env # set LUMIFY_API_KEY
npm start # → http://localhost:3000Documentation
API reference: https://lumify.ai/docs/reference
OpenAPI: https://lumify.ai/docs/openapi (schema:
/openapi.json· ReDoc · Swagger UI)Guides (incl. MCP): https://lumify.ai/docs/guides
Quick start:
docs/getting-started/quick-start.mdAgent cookbook:
docs/agent-cookbook.mdPostman collection:
docs/lumify.postman_collection.json
Support & contributing
Questions and bugs: open an issue
Contribution guidelines:
CONTRIBUTING.md
License
MIT © 2026 Lumify AI
Available Tools
10 toolsbatch_get_eventsARead-onlyIdempotentInspect
Get multiple events by id in one call — for agents that already have a list of ids and want full detail for each without one call per event. Max 25 ids. Returns full detail for every id that exists plus a not_found list for any that don't (never billed). Use get_event for a single id, or list_events / query_events to discover ids first.
Inputs: event_ids (required), bookmaker, include_odds, include_intelligence. Returns: total, events, not_found
get_eventARead-onlyIdempotentInspect
Get a single event with participants and venue. Optionally inline current odds and/or bet intelligence (+1 credit each, only charged when that data is actually available). Raises a not-found error if event_id doesn't exist. Use list_events / query_events to discover ids first, or batch_get_events to fetch several ids in one call.
Inputs: event_id (required), bookmaker, include_odds, include_intelligence. Returns: id, name, sport, venue, +5 more
get_oddsARead-onlyIdempotentInspect
Get current betting odds for an event: per-bookmaker lines and last-updated time. bookmaker defaults to pinnacle; use 'all' for every book (costs 1 credit per book returned). Returns available:false with no charge if odds aren't posted for this event yet. Use get_odds_history for line movement over time instead of the current line.
Inputs: event_id (required), bookmaker. Returns: event_id, available, bookmakers, last_updated
get_odds_historyARead-onlyIdempotentInspect
Get line-movement history for an event: a list of past odds snapshots (movements), each with its own timestamp, up to limit entries. bookmaker defaults to pinnacle. Use get_odds instead if you only need the current line.
Inputs: event_id (required), limit, bookmaker. Returns: total, event_id, movements
get_playerARead-onlyIdempotentInspect
Get a single player profile: name, sport, country, position/handedness, physical stats, current team, and tennis ranking if applicable. Raises a not-found error if player_id doesn't exist. Resolve ids via search_players.
Inputs: player_id (required). Returns: id, slug, sport, position, +10 more
get_player_eventsARead-onlyIdempotentInspect
List a player's events (schedule/results), paginated by id (after_id). Defaults to ±30 days around today when no date filter is given. Resolve player_id via search_players first.
Inputs: player_id (required), to, from, limit, +2 more. Returns: data, has_more, player_id, next_after_id
get_splitsARead-onlyIdempotentInspect
Get public betting splits (bets% and handle%) for an event: a consensus split plus a per-book breakdown, with a captured_at timestamp. Returns available:false with no charge if splits haven't been captured for this event yet.
Inputs: event_id (required). Returns: books, event_id, available, consensus, +1 more
list_seasonsARead-onlyIdempotentInspect
List seasons per sport/league, optionally filtered by sport or to the current season only. Returns each season's id, year, phase, start/end dates, and whether it is_current. Use list_sports for just each sport's current season.
Inputs: sport, current_only. Returns: total, seasons
list_teamsARead-onlyIdempotentInspect
List teams, paginated by id (after_id). Filter by sport, league, conference, division, country, active status, or name (q, partial match). Returns each team's id, slug, name, city, conference/division, and venue. Use get_team for full detail on one id once resolved here.
Inputs: q, limit, sport, active, +5 more. Returns: data, has_more, next_after_id
query_eventsARead-onlyIdempotentInspect
Search events with a natural-language query instead of structured filters — e.g. 'live nfl games today' or 'college basketball this week'. Rule-based (not an LLM): recognizes sport (nfl/nba/mlb/nhl/tennis/soccer/ncaaf/ncaab + aliases like hockey, american football, college basketball), status (live/final/upcoming/…), dates (today/tomorrow, this week, next N days, YYYY-MM-DD ranges). Bare 'football' is ambiguous and left unrecognized. Response includes interpreted filters, equivalent REST call, and unrecognized_terms. Prefer list_events when you already know the structured filters you want.
Inputs: query (required), limit. Returns: query, total, events, interpreted, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
The tools split cleanly across events, odds, teams, players, and seasons, and there are explicit cross-references (e.g., get_event vs batch_get_events vs list_events/query_events). The only mild overlap is that get_odds, get_odds_history, and get_splits all relate to betting data, but each targets a distinct data type: current lines, line movement, and splits.
Use of get_/list_/batch_/query_ conventions is mostly consistent: get_event, get_odds, get_player; list_teams, list_seasons; batch_get_events, query_events. One slight inconsistency is get_player_events (verb_noun_verb rather than get/get/list pattern) and list_teams/list_seasons vs batch_get_events, but overall naming is predictable.
10 tools is well-scoped for a sports intelligence API covering events, odds, teams, players, and seasons. Each tool maps to a distinct resource or data type, with no obvious bloat or redundancy.
The surface covers event retrieval (single, batch, query), odds, splits, teams, players, player events, and seasons. Notable gaps: there is no tool for listing or searching sports/leagues directly (list_sports is referenced but not present), and no get_team tool even though list_teams says to use get_team for full detail. Also search_players is referenced but not present. These are minor omissions since the described tools still cover core read-only workflows, but the cross-references reveal missing dependencies.
Maintenance
Related MCP Connectors
Live sports data: scores, play-by-play, box scores, odds and props. No key needed to start.
Sports odds, player props and source coverage for AI assistants. Connect with your own API key.
Sports data across 8 sports under one canonical schema — scores, stats, standings, Elo, odds
NBA and NFL model probabilities and edges beside live market prices. One free game a day.
Related MCP Servers
- FlicenseBqualityCmaintenanceEnables comprehensive Sleeper Fantasy Football integration with Claude, providing real-time player projections, historical performance analytics, league management, and waiver wire analysis. Supports advanced NFL metrics, lineup optimization, and matchup analysis for fantasy football decision-making.121-

PropLineofficial
AlicenseAqualityBmaintenanceLive sports betting odds, cross-book +EV, and graded player-prop resolution across 13 books.11648 npm1MIT- AlicenseBqualityBmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29159 npm3MIT
- FlicenseNot gradedqualityDmaintenanceProvides comprehensive sports intelligence including live scores, standings, schedules, betting odds, news, highlights, and more via SSE transport.-