sleeper-mcp
Related Servers
Alternatives to sleeper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables reading Sleeper fantasy football rosters, matchups, standings, news, chat, and pick'em entries, with optional write actions for setting lineups, claiming waivers, and proposing trades.39MIT
- AlicenseAqualityBmaintenanceProvides read-only access to the Sleeper Fantasy Sports API for league info, rosters, matchups, drafts, transactions, and player data.1872 npm1MIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Sleeper fantasy football data including user info, leagues, rosters, matchups, and NFL state through MCP tools.72 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI models to manage and query fantasy sports leagues through the Sleeper API, supporting tasks like player lookups, league activity, and draft management.72 npmMIT
- FlicenseAqualityCmaintenanceEnables natural language interaction with Sleeper Fantasy Football API data, allowing queries about leagues, players, matchups, draft results, and trade analysis.1321-
- FlicenseAqualityCmaintenanceEnables read-only access to Sleeper fantasy sports data, including users, leagues, rosters, matchups, transactions, drafts, players, trending activity, playoff brackets, traded picks, and sport state via MCP tools.18-
TDQS
Scored across 13 tools
Each tool targets a distinct resource/action: user lookup, leagues, rosters, matchups, transactions, drafts, and player resolution. Even similar-sounding tools like get_leagues vs get_league are clearly separated by scope (user-specific vs by ID). No overlapping purposes.
All tools follow a consistent verb_noun pattern in snake_case (get_* except resolve_players, which is still a clear verb_noun). The pattern is uniform and predictable across the entire set, making it easy for an agent to infer behavior.
13 tools is well within the ideal 3-15 range. Each tool serves a specific data retrieval need for the Sleeper fantasy football domain, and the set is neither sparse nor bloated.
The tool surface covers the core read-only workflows: user/league discovery, roster and matchup retrieval, transactions, drafts, and player resolution. The tools chain together cleanly (e.g., get_drafts feeds get_draft_picks, get_nfl_state provides week context for get_matchups), with no obvious dead ends or missing critical operations.