sleeper_mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sleeper_mcpWhat are my matchups for this week?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
sleeper_mcp
Local Model Context Protocol server for the Sleeper fantasy API. Tools are locked to the user and league IDs in your gitignored .env. The public API is read-only; no token is required.
Setup
Requires Node.js 20+.
cp .env.example .env
npm installnpm install is enough; Cursor compiles TypeScript on launch. Do not start the server with npx tsx — that pulls in a platform-specific esbuild binary and breaks when Cursor’s Node architecture differs from the one used to install dependencies.
Fill in .env:
SLEEPER_USER_ID=your_numeric_user_id
SLEEPER_LEAGUE_IDS=league_id_one,league_id_two
SLEEPER_SEASON=2025Look up
SLEEPER_USER_IDwithGET https://api.sleeper.app/v1/user/<username>.SLEEPER_LEAGUE_IDSis a required allowlist. Tools will not accept any other league.SLEEPER_USER_IDand eachSLEEPER_LEAGUE_IDSvalue must be numeric Sleeper ids.SLEEPER_SEASONis optional. If set, it must be a 4-digit year. If omitted, the server usesleague_seasonfromGET /v1/state/nfl.
Never commit .env. Cursor user MCP settings may set the same variables; existing environment values win over the file.
On start the server checks that the user exists and that every configured league belongs to that user for the season.
Related MCP server: sleeper-caffeine MCP
Cursor
.cursor/mcp.json launches the server with no IDs:
{
"mcpServers": {
"sleeper": {
"command": "node",
"args": ["scripts/launch.js"]
}
}
}Cursor runs that with its own Node (20+). The launcher compiles src/ to dist/ then starts the server, so you do not need tsx or a matching esbuild binary.
Enable the server in Cursor MCP settings. Keep real IDs out of any committed file; use .env or Cursor user MCP env overrides.
Tools
Tool | What it returns |
| Configured user ( |
| Allowlisted leagues only |
| Rosters with owner and player names |
| Week matchups paired by |
| Specific draft (order, settings, status). |
| Draft picks with player and owner names. |
| Current week / season |
If exactly one league is configured, league_id is optional on league-scoped tools.
Player IDs are resolved from a daily cache of GET /v1/players/nfl stored in gitignored .cache/players-nfl.json.
Scripts
npm start # compile + stdio MCP (same entry Cursor uses)
npm run build # compile only
npm test # mocked unit testsLog only to stderr. stdout is the MCP protocol channel.
Inspector
npx @modelcontextprotocol/inspector node scripts/launch.jsThis server cannot be deployed
Maintenance
Related MCP Connectors
Read-only fantasy analysis for ESPN, Yahoo, and Sleeper leagues via MCP
Read-only ESPN, Sleeper, and Fantrax fantasy leagues for Claude, ChatGPT, and other AI tools.
SportsDataIO MCP — wraps SportsDataIO's Big-Six sports data API (sportsdata.io)
ESPN MCP — keyless multi-sport live scores, teams, and news via ESPN's public site API.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides read-only access to the Sleeper Fantasy Sports API for league info, rosters, matchups, drafts, transactions, and player data.1870 npm1MIT
- 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 gradedqualityCmaintenanceMCP server for NFL fantasy football retrieval, providing access to NFL stats and Sleeper league data through retrieval-oriented tools.-
- 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