sleeper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Look up a Sleeper user by username or user_id. Usernames can change over time, so store user_id for future lookups. |
| get_leaguesB | Get all leagues a user belongs to for a given season. |
| get_leagueA | Get a specific league's details by league ID. |
| get_rostersA | Get all rosters in a league. Player IDs are annotated with player names (which may not load if the player cache is warm). |
| get_users_in_leagueA | Get all users (and their display names/team names) in a league. |
| get_matchupsA | Get all matchups in a league for a given week. Teams sharing a matchup_id face each other. Player IDs are annotated with names. |
| get_transactionsA | Get all transactions (trades, waivers, free agent adds/drops) for a league in a given week (round). |
| get_traded_picksA | Get all traded draft picks in a league, including future picks. |
| get_nfl_stateA | Get the current NFL season, week, and season type (pre/regular/post). |
| get_draftsB | Get all drafts for a league, sorted most recent to earliest. |
| get_draft_picksB | Get all picks in a draft. Player metadata (name, position, team) is included per pick. |
| get_trending_playersB | Get players trending based on add/drop activity. |
| resolve_playersA | Resolve a list of Sleeper player IDs (e.g. from rosters or matchups) into player names, teams, positions, and injury status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.