sleeper-caffeine MCP
Provides read-only access to Sleeper fantasy football leagues, enabling team snapshots, available players, matchups, trade context, and league history through standardized MCP tools.
README
Sleeper Caffeine
Sleeper Caffeine is an open-source, read-only fantasy football front office for the desktop. Connect a public Sleeper league, choose your roster, and use Codex to produce league-specific analysis grounded in live Sleeper data and current web research.
The first release is intentionally safe: it cannot change a lineup, submit a waiver claim, send a trade, or accept one.
What works today
- Multi-league onboarding from a Sleeper league URL or ID.
- Team selection with Sleeper names, avatars, roster IDs, and user IDs.
- A polished dashboard, full roster room, reserve/taxi handling, headshots, and fallbacks.
- Manual Sleeper refresh with an immutable local snapshot history.
- A live draft board with completed picks and upcoming native draft slots.
- On-demand AI cards for team analysis, trade ideas, and draft candidates.
- A persistent conversational analyst scoped to the active league.
- Live web research with an explicit distinction between search/discovery and cited sources.
- Waiver and weekly start/sit surfaces marked for activation when regular-season data is meaningful.
- A standalone Sleeper MCP server over stdio and an app-managed Streamable HTTP bridge.
Product principles
- League data first. Codex must read the Sleeper MCP before making league-specific claims.
- Refresh is deterministic. Refreshing Sleeper updates SQLite and invalidates stale reports; it never spends an AI turn.
- AI is explicit. Every report has its own Generate or Regenerate action.
- Search is not a source. Search discovers material. Reports cite the page actually used.
- Read-only means read-only. No Sleeper credentials, browser cookies, shell access, or hidden roster mutations.
- Local by default. League snapshots, reports, recommendation history, chat, and the isolated Codex home live on the user's machine.
Architecture
flowchart LR
Renderer["Electron renderer"] -->|typed IPC| Main["Electron main process"]
Main --> Store["SQLite snapshots + reports"]
Main --> Core["sleeper-core"]
Main --> Codex["Installed codex app-server"]
Codex -->|Streamable HTTP| MCP["Sleeper MCP bridge"]
MCP --> Core
Core --> API["Sleeper public API"]
Core --> Cache["24-hour player cache"]
Codex --> Web["Live web search"]
The renderer is sandboxed and receives only a narrow preload API. It never receives OpenAI tokens, raw child-process access, SQLite access, or arbitrary filesystem primitives.
Codex runs as one long-lived codex app-server process with:
- A dedicated
CODEX_HOMEinside the app's user-data directory. - Codex-managed ChatGPT OAuth.
- A read-only sandbox and
approvalPolicy: "never". - The shell tool disabled.
- Live web search enabled.
- The local Sleeper MCP configured automatically.
Sleeper Caffeine discovers Codex through CODEX_CLI_PATH, the user's PATH, or known Codex/ChatGPT application locations. It does not bundle a Codex binary.
Repository layout
apps/
desktop/ Electron + React desktop product
packages/
sleeper-core/ Sleeper API, schemas, joins, cache, domain logic
sleeper-mcp/ Standalone MCP plus stdio and HTTP transports
ipc-contract/ Renderer/main schemas and typed API
codex-runtime/ Binary discovery, JSONL RPC, OAuth, threads, turns
The desktop and MCP use the same sleeper-core; the UI never calls the MCP as an internal API.
Requirements
- Node.js 22 or newer.
- pnpm 10.
- An installed Codex CLI or an application that ships the Codex binary.
- A ChatGPT account for AI analysis. Sleeper browsing and roster views work without it.
Run locally
pnpm install
pnpm dev
Production build:
pnpm build
Package the current platform:
pnpm dist:mac
pnpm dist:linux
pnpm dist:win
The app is not yet signed or notarized. Local macOS builds may require the standard unsigned-app development workflow.
Standalone Sleeper MCP
The original adapter remains independently usable:
pnpm build:packages
pnpm --filter @sleeper-caffeine/mcp start
Example Codex CLI registration:
codex mcp add sleeper -- node /absolute/path/to/sleeper-caffeine/packages/sleeper-mcp/dist/src/index.js
Tools:
| Tool | Purpose |
|---|---|
get_team_snapshot |
Settings, joined roster, matchup, and traded-pick context. |
get_available_players |
Players absent from every current league roster. |
get_matchup_context |
Both sides of a weekly matchup with joined players. |
get_trade_context |
Every roster, traded picks, drafts, and selected transactions. |
get_league_history |
Linked historical seasons and obtainable champions. |
Sleeper's player directory is cached for 24 hours. “Available” means absent from current rosters; it does not prove waiver clearance or lineup eligibility.
Development checks
pnpm typecheck
pnpm lint
pnpm test
pnpm build
Read-only live checks are opt-in:
SLEEPER_LIVE_LEAGUE_ID=123456789012345678 \
SLEEPER_LIVE_USER=your_username \
pnpm test:live
The desktop also contains opt-in live coverage for onboarding and the Codex app-server handshake.
Data and privacy
- Sleeper's documented fantasy API is public and read-only; no Sleeper password is requested.
- ChatGPT login is managed and stored by Codex inside the app-specific
CODEX_HOME. - OpenAI access and refresh tokens are never exposed to the renderer or stored in SQLite.
- “Clear local league data” removes leagues, snapshots, reports, chats, thread references, and the player cache. It deliberately does not sign the user out of ChatGPT.
- The Athletic may appear in public search results, but this release does not automate a signed-in browser or bypass a subscription wall.
See SECURITY.md for reporting and trust boundaries.
Roadmap
- Regular-season waiver and start/sit intelligence.
- Faster live-draft polling and pick-aware candidate refresh.
- Recommendation outcomes and retrospective scoring.
- Additional projections/rankings adapters with clear licensing boundaries.
- Cross-platform release signing and auto-update infrastructure.
- Any future Sleeper write automation only as a separately designed, opt-in capability with explicit confirmations.
Contributing
Issues and pull requests are welcome. Start with CONTRIBUTING.md, and keep every proposed Sleeper integration read-only unless a future design document explicitly changes that boundary.
Sources
- Sleeper API documentation
- Model Context Protocol TypeScript SDK
- OpenAI Codex app-server documentation
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.