get_daily_scheduleLABSCO SUMMARY
A live MLB data feed an assistant can query by game, team, or player.
The tools map onto how baseball data is actually asked about — today's schedule, a game's box score or play-by-play, a player's splits, the current leaders — so an agent can go from the day's slate to a single game's pitch metrics without leaving the conversation.
What it is
A server that connects an assistant to the SportRadar MLB API, exposing game, team, and player data as tools: schedules and detailed game feeds, standings and rosters, player profiles and splits, and league-wide reports.
What you get
- Game data: get_daily_schedule, get_game_summary, get_game_boxscore, get_game_play_by_play, and get_game_pitch_metrics for pitch-level Statcast data
- Team and league: get_standings, get_team_profile, get_team_roster, get_team_hierarchy, and get_seasonal_statistics
- Players: get_player_profile, get_player_seasonal_stats, get_seasonal_splits, and get_league_leaders
- League information: get_injuries, get_transactions, and get_draft_summary
Requirements
Python and a SportRadar MLB API key; runs through the MCP CLI. Be mindful of the API's rate limits, which are lower on trial keys.
Setup effort
Follow the published steps — git clone https://github.com/robcerda/mlb-sportradar-mcp.git
USE CASES
01
Checking today's games and results
get_daily_schedule returns the day's slate and get_game_summary or get_game_boxscore gives the detail on any one of them.
02
Looking up where a division stands
get_standings returns standings for a season and league.
03
Digging into a player
get_player_seasonal_stats and get_seasonal_splits return a player's numbers and situational splits.
04
Following league movement
get_injuries and get_transactions report the current injury list and the day's roster moves.
17 tools
Listed in project docs. Your client may show a different list.
get_game_summaryget_game_boxscoreget_game_play_by_playget_game_pitch_metricsget_standingsget_team_profileget_team_rosterget_team_hierarchyget_seasonal_statisticsget_player_profileget_player_seasonal_statsget_seasonal_splitsget_league_leadersget_injuriesget_transactionsget_draft_summaryBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation. Every tool reads SportRadar's MLB API v8; trial keys typically get lower rate limits than production keys.
Requires
- Python 3.12 or later
- SPORTRADAR_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Sign up at the SportRadar Developer Portal and get an MLB API key (trial or production)
Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh
TERMINAL
git clone https://github.com/robcerda/mlb-sportradar-mcp.git
cd mlb-sportradar-mcpCreate and activate a virtual environment: uv venv then source .venv/bin/activate (Windows: .venv\Scripts\activate)
Install dependencies: uv sync (or pip install -r requirements.txt, or uv pip install -e .)
Create a .env file containing SPORTRADAR_API_KEY=<YOUR_SPORTRADAR_API_KEY>
Install the MCP CLI globally:
TERMINAL
uv tool install "mcp[cli]"Add the config block below to claude_desktop_config.json and restart Claude Desktop
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"MLB SportRadar": {
"command": "/Users/<YOUR_USERNAME>/.local/share/uv/tools/mcp/bin/mcp",
"args": [
"run",
"<YOUR_PATH_TO_MLB_SPORTRADAR_MCP>/src/mlb_sportradar_mcp/server.py"
]
}
}
}The configuration on this page does not set SPORTRADAR_API_KEY; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
