get_splits — Lumify Sports Intelligence MCP Tool Read-only
get_splits
(get splits) is one of 28 tools on the
Lumify Sports Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_splits from your client
- Claude Code Lumify Sports Intelligence get_splits run in your project directory
- Claude Desktop Lumify Sports Intelligence get_splits ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Lumify Sports Intelligence get_splits ~/.cursor/mcp.json
- VS Code Lumify Sports Intelligence get_splits .vscode/mcp.json
- Zed Lumify Sports Intelligence get_splits ~/.config/zed/settings.json
- Windsurf Lumify Sports Intelligence get_splits ~/.codeium/windsurf/mcp_config.json
- Cline Lumify Sports Intelligence get_splits ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Lumify Sports Intelligence get_splits ~/.gemini/settings.json
- Grok Lumify Sports Intelligence get_splits .mcp.json (in your project root)
- ChatGPT Lumify Sports Intelligence get_splits Settings → Connectors → Advanced → Developer mode
- Claude.ai Lumify Sports Intelligence get_splits Settings → Connectors → Add custom connector
- LangChain Lumify Sports Intelligence get_splits pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sports-intelligence https://lumify.ai/mcpOther tools on this server
- list_sports
- list_events
- get_event
- batch_get_events
- query_events
- get_live_score
- get_odds
- get_odds_history
- get_stats
- get_player_props
- get_team_props
- get_period_odds
- get_injuries
- get_intelligence
- list_ev
- list_forecasts
- list_teams
- search_players
- get_team
- get_player
- get_player_events
- list_seasons
- estimate_cost
- resolve_player
- resolve_team
- resolve_event
- grade_slip
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.