Sportmonks MCP Server
Related Servers
Alternatives to Sportmonks MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides real-time access to football (soccer) data including fixtures, standings, teams, players, transfers, and injuries through the API-Football service via the Model Context Protocol.3-
- AlicenseNot gradedqualityDmaintenanceMCP server for football-data.org API providing access to football data like standings, matches, teams, and scorers.MIT
- AlicenseAqualityAmaintenanceA unified MCP server that aggregates 32 sports API providers into a single service, providing 336 tools for scores, stats, odds, esports, and more across 70+ sports.10043 npm22MIT
- FlicenseBqualityDmaintenanceA unified MCP server that combines The Odds API and SportMonks Football API v3 to provide 28 tools for sports data like odds, scores, fixtures, standings, and predictions, enabling Claude to interact with a wide range of sports information.281-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables agents to interact with soccer data including scores, matches, players, and teams using the sportsdata.io Soccer V3 Scores API.-
- AlicenseBqualityAmaintenanceA Model Context Protocol server that provides access to Fantasy Premier League data, allowing users to compare players, find team information, view gameweek data, and get FPL-related advice through Claude for Desktop and other MCP-compatible clients.23120 PyPI80MIT
TDQS
Scored across 171 tools
Each tool name clearly indicates the entity and action (e.g., get_all_fixtures, get_fixture_by_id, search_players_by_name). There is no ambiguity between similar tools because they are distinguished by parameters like date range, team, or entity type.
All tool names follow a consistent pattern: 'get_all_<plural>' for lists, 'get_<singular>_by_id' for single entities, 'get_<entity>_by_<filter>' for filtered queries, and 'search_<entity>_by_name' for searches. Lowercase snake_case is used uniformly.
With 171 tools, the count is extremely high. Even for a broad sports data API, this number exceeds typical scopes and can overwhelm an LLM agent. Many tools could be consolidated (e.g., using filters instead of separate endpoints).
The toolset covers a wide range of sports data entities (fixtures, odds, teams, players, leagues, seasons, transfers, etc.) and includes search, odds, and statistics. Minor gaps exist (e.g., no player statistics per season, no write operations), but overall it is comprehensive for a read-only sports data API.