mlb-api-mcp
Related Servers
Alternatives to mlb-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP Server that enables interaction with MLB scores and statistics via the SportsData.io MLB V3 Scores API, allowing users to access baseball data through natural language queries.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with MLB (Major League Baseball) v3 projections through the SportsData.io API, allowing access to baseball statistics and projections through natural language.-
- AlicenseAqualityDmaintenanceAn MCP Server implementation that integrates the Balldontlie API, to provide information about players, teams and games for the NBA, NFL and MLB.441 npm26MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for natural language analysis of baseball league data, enabling team statistics, standings, lineup suggestions, and scouting reports via Claude Desktop.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server for accessing college basketball statistics through the SportsData.io CBB v3 Stats API, enabling AI agents to retrieve and analyze college basketball data through natural language interactions.-
- FlicenseNot gradedqualityDmaintenanceA Python-based MCP server that exposes tools over streamable HTTP using FastAPI, enabling connection to AI assistants like Cursor. Supports multiple servers mounted in a single FastAPI app.-
TDQS
Scored across 24 tools
Most tools have distinct purposes targeting specific MLB resources like games, players, teams, and statistics. However, some overlap exists between get_mlb_player_info and get_mlb_players, and between get_mlb_team_info and get_mlb_teams, which could cause minor confusion. The Statcast tools are clearly differentiated by batter/pitcher/team focus.
All tools follow a consistent get_* prefix pattern with snake_case naming. The naming convention is uniform throughout, with clear verb_noun structure (e.g., get_mlb_boxscore, get_mlb_schedule, get_statcast_batter). No mixing of naming styles or inconsistent patterns.
24 tools is borderline heavy for an MLB API server. While MLB has many data dimensions, this feels like it could be consolidated (e.g., multiple player/team retrieval tools). The count suggests potential redundancy rather than comprehensive coverage of distinct operations.
The toolset provides extensive read-only coverage of MLB data including games, players, teams, statistics, and advanced metrics. Minor gaps exist in write operations (no create/update/delete tools) and some specialized queries, but for a data retrieval API this is reasonably complete for agent workflows.