Sleeper Fantasy Football MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLEEPER_USER_ID | No | Stable user ID; takes precedence over the username. Alternative to SLEEPER_USERNAME. | |
| SLEEPER_USERNAME | No | Sleeper username used to locate the account. Required unless SLEEPER_USER_ID is provided. | |
| SLEEPER_CACHE_DIR | No | Override the local directory for the public player cache. | |
| SLEEPER_DEFAULT_SEASON | No | Four-digit season used when a tool does not provide one. |
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 |
|---|---|
| sleeper_accountB | Resolve the configured Sleeper username to its stable user ID and return the current NFL state. |
| sleeper_list_leaguesA | List the configured user’s NFL leagues for a season. Use this first to map league names to league IDs. |
| sleeper_league_overviewA | Get league rules, scoring, lineup slots, team directory, records, drafts, traded picks, and calculated future pick ownership. Does not include every player on every roster. |
| sleeper_my_rosterA | Get the configured user’s live roster in one league, resolved to player names and grouped into starters, bench, reserve, taxi, and keepers, plus draft-pick ownership. |
| sleeper_all_rostersA | Get every team’s live roster in a league with player names, positions, teams, injury status, records, FAAB, and lineup grouping. Useful for league-wide comparisons. |
| sleeper_trade_contextA | Get focused trade-analysis context for selected teams: full rosters, league rules, records, and future pick inventories. Teams can be identified by roster ID, owner name, username, or team name. Pending private trade offers are not exposed by the official API, so the offer itself must be pasted or described. |
| sleeper_transactionsA | Get and resolve completed or pending transaction records—trades, waivers, and free-agent moves—for a league and week range. Defaults to the current week and previous three weeks. |
| sleeper_matchupsA | Get one league week’s matchups with resolved starters, bench players, lineup slots, and current points. |
| sleeper_draft_boardA | Get a live or completed draft board, resolved player picks, draft order, and traded draft slots. Provide a league ID to use its newest draft, or a specific draft ID. |
| sleeper_search_playersA | Search Sleeper’s player directory by name and optionally position. Useful for resolving names mentioned in a proposed trade. |
| sleeper_trending_playersA | Get players most frequently added or dropped on Sleeper over a recent time window. |
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 11 tools
Each tool targets a distinct resource or workflow, from account resolution to rosters, transactions, matchups, and drafts. A few tools overlap in raw data—like all_rosters, my_roster, and trade_context all exposing roster info—but their scopes are clearly differentiated by descriptions.
All tools share the consistent 'sleeper_' prefix and use snake_case, making the namespace predictable. Naming style varies between verb-led (list_leagues, search_players) and noun-led (account, transactions, matchups), but the pattern is still coherent and readable.
Eleven tools is a well-scoped count for a fantasy football data server. Each tool covers a meaningful slice of the domain—leagues, rosters, trades, transactions, matchups, drafts, and player discovery—without unnecessary duplication.
The toolset comprehensively covers the read-only Sleeper fantasy football domain: account identity, leagues, rosters, trade context, transactions, matchups, drafts, and player search/trending. There are no obvious dead ends for typical fantasy football analysis workflows.