sleeper-mcp
Related Servers
Alternatives to sleeper-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables access to Sleeper fantasy football data, including users, leagues, rosters, matchups, transactions, drafts, and player information.1312 npm-
- FlicenseAqualityDmaintenanceEnables natural language interaction with Sleeper Fantasy Football API data, allowing queries about leagues, players, matchups, draft results, and trade analysis.1325-
- AlicenseAqualityDmaintenanceProvides read-only access to the Sleeper Fantasy Sports API for league info, rosters, matchups, drafts, transactions, and player data.1879 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI models to manage and query fantasy sports leagues through the Sleeper API, supporting tasks like player lookups, league activity, and draft management.79 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP clients to query Sleeper fantasy football leagues, rosters, drafts, picks, and NFL player data, including a normalized on-the-clock draft view. It also supports AI-vs-AI mock draft simulation using real league settings.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables remote access to Sleeper fantasy football leagues via an MCP endpoint, providing read-only tools for league snapshots, transactions, traded picks, and computed free agents to any MCP client.79 npmMIT
TDQS
Scored across 39 tools
Despite 39 tools, descriptions sharply delineate each purpose: player_news vs player_outlook vs player_signal, playoff_odds vs playoff_bracket, and waiver_targets vs breakouts are all explicitly contrasted. A few near-neighbors (player_signal/signal_divergence, watch_player/watched_players) require reading descriptions but are not truly overlapping.
All names use a single snake_case convention with no camelCase mixing, and verb_noun or noun patterns are consistently applied (cancel_claim, set_lineup, propose_trade, standings, matchup). Minor inconsistency in that some entries are pure nouns and others verb_noun, but the style is uniform and readable.
39 tools is well past the heavy end, forcing broad selection across reads, writes, simulations, and pick'em. Each tool is arguably distinct, but the surface is large enough that consolidating analytics/read variants would reduce selection load.
The surface covers the full lifecycle: roster/lineup, waivers (claim/cancel), trades (propose/respond/pending), IR, keepers, draft, standings, matchups plus deep analytics and auth/setup helpers. Coverage is unusually thorough, with only minor gaps (e.g. no standalone drop without a waiver path).