sleeper-mcp
Related Servers
Alternatives to sleeper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Sleeper fantasy football data including user info, leagues, rosters, matchups, and NFL state through MCP tools.77MIT
- AlicenseAqualityBmaintenanceProvides read-only access to the Sleeper Fantasy Sports API for league info, rosters, matchups, drafts, transactions, and player data.18771MIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to Sleeper fantasy football leagues, enabling team snapshots, available players, matchups, trade context, and league history through standardized MCP tools.MIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server that provides access to public Sleeper NFL fantasy data, including leagues, rosters, matchups, waivers, drafts, and player information. It enables AI clients to retrieve fantasy football details without requiring authentication or account modifications.-
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to DraftKings DFS lobby data, including slates, contests, salaries, and roster rules, via MCP.-
- AlicenseAqualityCmaintenanceA read-only MCP server that supplies live context from Sleeper fantasy-football leagues, including rosters, trade analysis, draft picks, and league settings via Sleeper's public API.11MIT
TDQS
Scored across 18 tools
Each tool targets a distinct resource or scope: user profiles, league members/rosters, matchups, winners vs losers brackets, league-level vs draft-level traded picks, and player lookup vs trending. The few names that share terms are clearly differentiated by their scope qualifiers and descriptions.
All tools use a consistent get_ prefix and snake_case noun-based naming, and related resources share clear patterns like get_league_*, get_user_*, and get_draft_*. There are no mixed conventions or unpredictable verb choices.
At 18 tools, this is above the typical 3–15 sweet spot, but the server is scoped to the broad Sleeper fantasy sports API and every tool maps to a meaningful endpoint. The count is on the higher end but still reasonable given the domain.
The surface covers the full read-only Sleeper workflow: user resolution, league discovery, rosters, users, matchups, playoff brackets, transactions, traded picks, sports state, drafts, draft picks, player lookup, and trending players. There are no obvious dead ends because the descriptions include explicit chaining between related tools.