Lumify
Lumify provides sports schedules, live scores, odds, statistics, and explainable betting intelligence through a credit-metered API.
Verdict
Common use cases
- Pull live scores during game-day Slack threads
- Compare odds movement across multiple sportsbooks
- Research player matchup history for fantasy lineups
- Estimate credit costs before bulk event queries
- Monitor league schedules and filter by date range
Integration
- Vendor
- Lumify
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
lumify
Tools
- Get Credit Usage
Get the Lumify account tier, usage, limits, trial state, and remaining credits. The response body is a pre-call snapshot and this request costs one credit. When Lumify returns X-Credits-Remaining, the result also includes the authoritative
- Get Event Analysis
Fetch selected intelligence, odds, odds history, public splits, and/or deterministic stats for one event. Each selected section makes a separate request against Lumify's 20 requests-per-minute limit. Unavailable sections are successful zero
- Get Events
Fetch full details for 1-25 event IDs in one API request, optionally including odds or intelligence. Credits are charged per found event, duplicate IDs are billed once, and missing IDs are returned in not_found as partial success.
- Get Event Score
Get a compact current score and status snapshot for one Lumify event. A successful available response normally costs 1 credit and consumes 1 of the connected key's 20 requests per minute.
- List Events
Find scheduled, live, or historical Lumify events with structured filters and one-page cursor pagination. A successful page normally costs one credit and uses one request from the connected key's rate limit.
- List Player Events
List one Lumify player's schedule and results with date and status filters, returning one cursor-controlled page. A successful page normally costs one credit and uses one request from the connected key's rate limit.
- List Sports or Seasons
List Lumify sports and leagues or seasons. Use this reference lookup before filtering events by sport, league, or season identifier.
- Plan Credit Costs
Discover Lumify estimator tool identifiers or estimate credit ranges for up to 50 planned calls without executing them. Both modes cost zero credits but consume one request from Lumify's rate limit. Omit calls for discovery.
- Search Players
Search Lumify players by sport, partial name, country, activity, or tennis ranking and return one cursor-controlled page. A successful page normally costs one credit and uses one request from the connected key's rate limit.
- Search Teams
Search teams by sport, league, conference, division, country, active status, or partial team name and return one cursor-controlled page. A successful page normally costs 1 credit and consumes 1 of 20 requests per minute.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings → Integrations → Browse MCP Servers. 2. Search for Lumify and click Connect. 3. Switchy will prompt you for a Lumify API key — log into your Lumify account, go to API Settings, and generate a new key with read access to events, odds, and player data. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection and displays your current credit balance and rate limit. 6. Open any Project, type '@Lumify get event score' followed by an event ID, and send the message. 7. Lumify returns the live score and status in the thread. 8. Check the response header for remaining credits so you can track usage as you work.
What teammates see: by default, memories from Lumify are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Live Score Check
@Lumify get event score for event ID 987654. Show me the current score, quarter, and time remaining.
Odds History Snapshot
@Lumify get event analysis for event ID 123456, including odds history and public splits from the past 48 hours.
Player Schedule Lookup
@Lumify list player events for player ID 78910, filtering for games scheduled in the next two weeks.
Bulk Event Details
@Lumify get events for IDs 111222, 333444, 555666, and include current odds for each game.
Credit Budget Planning
@Lumify plan credit costs for fetching event analysis on 20 games and listing player events for 5 athletes.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Lumify list tonight's NBA games with current odds and show me which matchups have the biggest line movement in the last 3 hours
Found 8 NBA games scheduled for tonight. The Lakers vs. Celtics spread moved from LAL -4.5 to -6.0 in the past 3 hours (largest shift), while the Nuggets vs. Suns total climbed from 225.5 to 228.0. The Warriors vs. Mavericks line held steady at GSW -2.5. Public betting splits show 68% on the Lakers spread. This query consumed 2 credits: one for the event list, one for odds history on the 8 games.
This example shows Lumify's real-time odds tracking and line-movement detection. Each odds-history section costs additional credits, so filtering to fewer games before requesting historical data keeps costs predictable. Rate limit is 20 requests per minute across all tools.
@Lumify get detailed intelligence and deterministic stats for event ID evt_abc123 including injury reports and recent head-to-head performance
Event evt_abc123 (Celtics @ Heat, tip-off 7:30 PM ET): Celtics are 3-1 in last 4 meetings, averaging 112 PPG. Heat list Jimmy Butler as questionable (ankle). Deterministic stats show Boston's offensive rating at 118.2 vs. Miami's defensive rating of 110.5. Public splits: 62% on Celtics moneyline. Intelligence and stats sections each triggered separate API calls; total cost was 3 credits for this event.
Lumify's event-analysis tool fetches intelligence, odds history, and stats as separate billable sections. Requesting all sections for one event is thorough but credit-intensive. Use this when deep context justifies the cost; for bulk screening, start with the cheaper list-events tool.
@Lumify check my account usage and estimate credit cost if I fetch full event details with odds for 15 upcoming MLB games, then tell me if I have enough credits left
Your Lumify account is on the Pro tier with 1,240 credits remaining this billing cycle (resets in 18 days). Estimating your planned query: fetching 15 events with odds will cost approximately 30 credits (2 per event). You have sufficient credits. Current rate-limit headroom: 20 requests per minute. Note that the usage snapshot itself consumed 1 credit, and the cost estimate consumed 1 request against your rate limit but zero credits.
This example pairs Lumify's credit-usage tool with its cost-estimation planner, letting the AI reason about budget before executing expensive queries. The planner is free (credits-wise) but still counts toward the 20-req/min limit. Useful for teams managing shared API keys.
Use-case deep-dives
When Lumify wins for real-time odds tracking
A 6-person mobile app team building a live-betting companion needs odds, scores, and event intelligence refreshed every 30 seconds across 15 concurrent games. Lumify's Get Event Score and Get Event Analysis tools deliver the snapshot data without forcing you to poll a generic sports API that charges per field. The 20-requests-per-minute rate limit means you can track roughly 10 events in parallel if you're smart about batching—fine for a beta with under 500 concurrent users. Once you cross 1,000 users or need sub-10-second refresh, you'll hit the rate ceiling and need to cache aggressively or move to a WebSocket provider. If your feature is "show live odds in-app" and you're pre-product-market-fit, Lumify's credit model and structured intelligence endpoints let you ship faster than stitching together three separate feeds.
When Lumify's player event history saves analyst time
A 3-person fantasy analytics startup needs historical performance, injury context, and matchup intelligence for 200+ players each week. Lumify's List Player Events and Get Event Analysis tools return structured stats and odds history in one call per player, so your analyst doesn't spend Friday morning copy-pasting from five different sites. The Plan Credit Costs tool lets you budget your monthly spend before running bulk queries—critical when you're bootstrapped and every credit matters. The catch: if you need play-by-play granularity or custom stat definitions, Lumify's deterministic stats won't cover it, and you'll still need a raw feed. If your workflow is "pull last 10 games for each player, rank by Lumify's intelligence score, export to spreadsheet," this MCP turns a 4-hour manual task into a 10-minute Switchy prompt.
When Lumify answers "why did the line move" tickets
A 12-person support team at a regional sportsbook gets 40 tickets a day asking why odds shifted or why a bet graded a certain way. Lumify's Get Event Analysis and odds history endpoints give your agents the same intelligence feed your trading desk sees—public splits, line movement timestamps, and injury flags—so they can answer "the line moved because 80% of bets came in on the favorite" without escalating to ops. The Get Credit Usage tool keeps the support lead honest about monthly burn; at one credit per lookup, 800 tickets a month costs you 800 credits, which fits most mid-tier plans. If your ticket volume spikes above 2,000 a month or you need to embed odds data in your CRM, you'll want a dedicated Lumify enterprise key with higher rate limits. For a support team that just needs to look up "what happened in this game" a few dozen times a day, this MCP beats giving every agent a separate Lumify login.
Frequently asked
What does the Lumify MCP do in Switchy?
It connects your Switchy workspace to Lumify's sports data API, letting AI agents fetch live scores, event schedules, odds, player stats, and betting intelligence across leagues. Agents can query upcoming games, pull historical results, or check your account's credit balance without leaving the conversation. Useful for teams building sports analytics, betting tools, or content workflows that need real-time data.
Do I need a paid Lumify account to use this MCP?
Yes. You need an active Lumify API key, which comes with a paid plan or trial. The MCP authenticates with that key and every request consumes credits from your Lumify account. Free tiers or expired trials won't work. Check your usage with the Get Credit Usage tool before running large queries to avoid hitting your limit mid-workflow.
Can the Lumify MCP place bets or modify odds?
No. It's read-only. The MCP fetches odds, scores, and intelligence but can't place wagers, update lines, or write data back to Lumify. If your team needs to act on the data—like triggering a bet—you'll build that logic separately using Lumify's transactional APIs or a sportsbook integration outside Switchy.
Why use this MCP instead of calling Lumify's API directly?
The MCP wraps Lumify's endpoints so your AI agents can query sports data in natural language without writing code. Instead of scripting pagination or parsing JSON, you ask "show me tonight's NBA games" and the agent handles the API call. Faster for exploratory work, slower if you're processing thousands of events in batch.
Does Lumify MCP usage count against Switchy's plan limits?
No. Switchy doesn't meter Lumify requests—your Lumify account does. Each tool call consumes credits and counts toward Lumify's 20-requests-per-minute rate limit. If you hit that ceiling, the MCP will fail until the window resets. Monitor your Lumify dashboard to avoid surprise overages during high-volume workflows.