sleeper-mcp
# sleeper-mcp
MCP server exposing the [Sleeper](https://sleeper.app) fantasy football API.
## Setup
```bash
npm install
npm run build
```
## Tools
| Tool | Description |
|------|-------------|
| `get_user` | Look up user by username or user_id |
| `get_leagues` | All leagues for a user in a season |
| `get_league` | Single league details |
| `get_rosters` | All rosters (player IDs enriched with names) |
| `get_users_in_league` | Users with display names and team names |
| `get_matchups` | Weekly matchups (player IDs enriched with names) |
| `get_transactions` | Trades, waivers, FA adds/drops by week |
| `get_traded_picks` | All traded draft picks including future |
| `get_nfl_state` | Current NFL season/week |
| `get_drafts` | All drafts for a league |
| `get_draft_picks` | Picks in a specific draft |
| `get_trending_players` | Trending adds/drops with player names |
| `resolve_players` | Resolve player IDs to names/teams/status |
## Notes
- Read-only API; no auth required
- Player names are automatically resolved where possible (rosters, matchups, trending)
- `resolve_players` tool can look up any player ID on demand
- Stay under ~1000 API calls/min to avoid rate limits
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.