Menyediakan AI client dengan analitik NFL fantasy football secara live, termasuk statistik pemain, nilai dynasty, data liga Sleeper, dan proyeksi Excel kustom.
Juga dikenal sebagai dachhack/stathead
- Stars
- 3
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 1.0.126
- Commit terakhir
- 15 Nov 2026
- Lisensi
- MIT
Apa itu StatHead MCP?
StatHead adalah MCP server. Menyediakan AI client dengan analitik NFL fantasy football secara live, termasuk statistik pemain, nilai dynasty, data liga Sleeper, dan proyeksi Excel kustom.
Ringkasan dibuat dari README proyek
Tentang StatHead MCP server
Penggemar dan analis fantasy football dapat mengakses data NFL live dan nilai dynasty secara langsung melalui AI client seperti Claude Desktop, Cursor, atau Claude Code. Server ini menyediakan lebih dari 50 tools yang mencakup segalanya, mulai dari statistik musim pemain dan snap counts hingga Next Gen Stats tingkat lanjut dan laporan cedera. Server ini terhubung secara mendalam dengan liga Sleeper, memungkinkan pengguna untuk memeriksa klasemen, roster, transaksi, bahkan exposure manajer antar liga.
Pengguna dapat mengelola ranking dan proyeksi kustom mereka sendiri dengan mengekspor data ke Excel, melakukan pengeditan manual, dan mengimpor kembali file tersebut untuk menimpa model internal server. Pengaturannya sangat mudah menggunakan npx untuk eksekusi lokal via stdio, atau dapat digunakan sebagai remote connector melalui URL yang dihosting. Meskipun sebagian besar data berasal dari upstream terbuka seperti nflverse dan Sleeper, fitur spesifik seperti odds taruhan memerlukan API key eksternal.
Apa yang bisa Anda lakukan dengannya
- 1Analisis aktivitas liga SleeperMinta AI untuk meninjau transaksi terbaru dan pergerakan waiver wire dalam liga Sleeper tertentu.
- 2Evaluasi nilai trade dynastyTentukan nilai pasar yang adil dari seorang pemain menggunakan data trade historis Sleeper dan prakiraan masa depan.
- 3Nilai tingkat kesulitan matchup mingguanIdentifikasi pemain mana yang memiliki jadwal mendatang paling mudah berdasarkan poin pertahanan yang diizinkan.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal StatHead MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal StatHead MCP di Claude Code
$ claude mcp add stathead-mcp -- npx -y stathead-mcpInstal StatHead MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"stathead-mcp": {
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}Instal StatHead MCP di VS Code
.vscode/mcp.json
{
"servers": {
"stathead-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}Instal StatHead MCP di VS Code CLI
$ code --add-mcp '{"name":"stathead-mcp","type":"stdio","command":"npx","args":["-y","stathead-mcp"]}'Instal StatHead MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"stathead-mcp": {
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}Instal StatHead MCP di Codex
$ codex mcp add stathead-mcp -- npx -y stathead-mcpInstal StatHead MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.stathead-mcp] command = "npx" args = ["-y", "stathead-mcp"]
Instal StatHead MCP di Gemini CLI
$ gemini mcp add -s user stathead-mcp npx -- -y stathead-mcpInstal StatHead MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"stathead-mcp": {
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaudachhack/stathead is public and reachablegithub.com/dachhack/stathead ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyastathead-mcp names dachhack/stathead as sourcenpmjs.com/package/stathead-mcp ↗Lolos
- Provenance build (atestasi Sigstore)Sigstore attestation for stathead-mcpnpmjs.com/package/stathead-mcp/v/1.0.126#provenance ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-12github.com/dachhack/stathead ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from stathead-mcpLolos
- Tidak ada advisory kritis pada paket atau dependensinya1 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubstathead-mcp
An MCP server that exposes StatHead's NFL fantasy-analytics toolset to Claude (Desktop / Code), Cursor, or any MCP client — so you can ask natural-language questions and get live, structured NFL data back.
It ships as a single self-contained bundle with no runtime dependencies and
fetches all data on demand, so there's nothing to download or build — npx and
go.
What you get
50 tools spanning player and team data, including:
| Area | Tools |
|---|---|
| Discovery | get_metadata — sources, season coverage, and valid enums (call this first to scope a question) |
| Players | season stats, weekly/game logs, snap counts, injuries, advanced stats, Next Gen Stats, rosters, contracts, get_depth_charts (slot-aware team depth charts with roster status, StatHead depth order and view=changes for moves) |
| Games & plays | schedules/results, play-by-play, participation, FTN charting |
| Fantasy | StatHead blended dynasty values, get_trade_values (StatHead values fitted to millions of completed Sleeper dynasty trades: as-of weekly values with 90% ranges, movers, liquidity, scoring re-pricing, 1/3/6/12-month forecasts, rookie-pick classes and history), get_projections (StatHead's in-house season PPG model), get_weekly_projections (per-week matchup-adjusted points, weeks 1–18), get_matchups (weekly strength of matchup: fantasy points each defense allows per game to QB/RB/WR/TE, ranked 1–32 in your scoring and over expected, by week, per player, rest of schedule, or split by metric such as TE receptions or QB rushing), ADP (FFC / ESPN / Sleeper), get_adp_with_results (ADP vs actual finish), trending adds/drops |
| Sleeper leagues | get_sleeper_user_leagues, get_sleeper_league (standings + rosters), get_sleeper_league_users (cheap manager list), get_sleeper_matchups, get_sleeper_transactions (trades/waivers/adds), get_sleeper_waiver_wire (free agents × trending × projections), get_sleeper_draft, get_sleeper_user_snooper (cross-league exposure), get_sleeper_user_history (multi-season records + titles) — a connected graph: a username lists leagues, a league name (or id) opens that league, and each manager's owner_id/display name walks back to their leagues, exposure, and history |
| Draft & college | get_prospect_outcomes (calibrated boom/bust probabilities + grades), draft picks, get_rookie_class (draft+combine+rookie stats in one call), prospect profiles, combine, college stats (player or cohort), QBR |
| Model & methodology | get_model_docs (how the models work + per-position feature importance), get_player_features (why a player is scored the way they are — feature drivers, bands, direction) |
| Your own numbers | export_excel / import_excel / clear_overrides — download a styled projections / rankings / rookie-rankings workbook (or a by_team projection sheet with live PPR formulas), edit it, re-upload it, and have your values drive every later query |
Bring your own projections & rankings
The same boards the website lets you download are available over MCP as real
.xlsx files (built with zero extra dependencies — Node's own zlib):
export_excel kind="projections"(orrankings,rookie_rankings) writes a styled workbook to disk and returns its path. Edit the highlighted column — Proj PPG for projections, My Rank for rankings/rookies — in Excel or Google Sheets.import_excel path="…"reads it back and saves your values as overrides.get_projections,get_fantasy_rankings, andget_prospect_outcomesthen automatically use your numbers (flagged in the output) until you runclear_overrides.
Workbooks default to $STATHEAD_DIR (or the current working directory); pass
path to choose where they land. Overrides persist in
$STATHEAD_DIR/~/.stathead/overrides.json.
Quick start
Run it directly — no install, no clone:
npx -y stathead-mcp
It speaks MCP over stdio, so you normally wire it into a client rather than run it by hand.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"stathead": {
"command": "npx",
"args": ["-y", "stathead-mcp"]
}
}
}
Claude Code
claude mcp add stathead -- npx -y stathead-mcp
Cursor / other MCP clients
Use the same command/args (npx -y stathead-mcp) in the client's MCP
config.
Claude mobile apps / claude.ai web / Claude Desktop (remote connector)
Prefer a URL over a local command? The same tools are hosted over MCP's
Streamable HTTP transport by a Cloudflare Worker (workers/stathead-mcp/,
deployed via deploy-workers.yml):
https://stathead-mcp.dachhack.workers.dev
Add it under Settings → Connectors → Add custom connector, paste the URL,
and save — no command, no API key. (A GET to that URL returns a small health
payload; clients POST JSON-RPC to it.) The npm/stdio package above stays the
path for Claude Code and Cursor.
The Worker records a privacy-respecting usage counter (MCP method + tool name
only — no IPs or request bodies) to a Cloudflare Analytics Engine dataset
(stathead_mcp_usage). View aggregates at GET /stats once you set the
CF_ACCOUNT_ID + CF_ANALYTICS_TOKEN worker secrets (wrangler secret put …),
or query the dataset in the Cloudflare dashboard. npm download counts don't see
remote-connector usage — this does.
Data sources & freshness
Most tools fetch live from open upstreams (nflverse, Sleeper, FantasyFootballCalculator, ESPN's public endpoints). A handful read committed daily snapshots (StatHead's blended dynasty values, ADP history, in-house season projections), which the server fetches from the hosted StatHead site by default.
Please review DATA_SOURCES.md before redistributing
any data this server returns — several upstreams are proprietary or paid and
carry their own terms.
Configuration
All optional, via environment variables:
| Var | Default | Purpose |
|---|---|---|
STATHEAD_DATA_BASE |
GitHub raw (data branch) | Base URL for committed snapshot data (<base>data/<file>). Defaults to GitHub raw, which serves every file uncompressed/reliably (the Cloudflare host gzips files over its 25 MiB cap, which Node can't decode). Override to point at your own deployment or a local http://localhost:5173/ dev server. |
VITE_KTC_PROXY |
project worker | CORS proxy for KeepTradeCut. Deploy your own (workers/ktc-proxy) to avoid shared rate limits. |
VITE_FC_PROXY |
project worker | CORS proxy for FantasyCalc (workers/fc-proxy). |
VITE_ODDS_API_KEY |
— | Enables betting-odds tools (the-odds-api.com). |
Running from a full repo checkout instead? The server reads snapshots straight
from local public/data/ and ignores STATHEAD_DATA_BASE.
Building from source
The bundle is produced from the StatHead monorepo:
# from the repo root
npm install
npm run build:mcp # → mcp/dist/server.mjs (esbuild, single file)
node mcp/dist/server.mjs
Publishing
Bump version in mcp/package.json and SERVER_VERSION in
mcp/dist/server.mjs (they must match), merge to the default branch, then
any one of:
git push -f origin <commit>:publish-mcp-now # branch-push trigger (works from Claude Code sessions)
git tag mcp-v1.2.3 && git push origin mcp-v1.2.3 # tag trigger
# or Actions → "Publish stathead-mcp to npm" → Run workflow
publish-mcp.yml refuses a version already on npm and a commit not yet on
the default branch, smoke-tests the bundle, publishes via npm Trusted
Publishing, then chains the MCP Registry publish. Manual fallback:
npm run build:mcp # repo root — refresh the bundle
cd mcp && npm publish --access public
The published tarball is just dist/server.mjs + this README (~220 KB).
Listing in the MCP Registry
server.json is the manifest for the official MCP Registry
(io.github.dachhack/stathead-mcp). After an npm publish, the
Publish to MCP Registry workflow (.github/workflows/publish-mcp-registry.yml)
pushes it — authenticating via GitHub OIDC for the io.github.dachhack/*
namespace (no secret). The npm package carries a matching mcpName field so the
registry can verify the package belongs to this entry, and the workflow syncs
server.json's version from package.json so they never drift.
Most community directories (Glama, mcp.so, PulseMCP) mirror the official
registry and/or auto-index public npm packages with the model-context-protocol
keyword (which package.json has), so a registry publish propagates to them.
License
MIT — see ../LICENSE. The code is MIT; the data it returns
is not necessarily redistributable. See
DATA_SOURCES.md.
Pertanyaan tentang StatHead MCP
Bagaimana cara menambahkan StatHead MCP ke Claude Code?
Jalankan claude mcp add stathead-mcp -- npx -y stathead-mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan StatHead MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana cara menggunakan proyeksi dan ranking saya sendiri?
Anda dapat mengekspor proyeksi atau ranking ke file Excel, mengedit nilainya di Excel atau Google Sheets, lalu mengimpor kembali file tersebut untuk menggunakan nilai tersebut sebagai override dalam query Anda.
Apakah server ini memerlukan runtime dependencies untuk dijalankan?
Tidak, ini adalah bundle mandiri tunggal tanpa runtime dependencies yang mengambil semua data sesuai permintaan.
Bisakah saya menggunakan ini dengan Claude Desktop?
Ya, Anda dapat menambahkannya ke file konfigurasi Claude Desktop Anda menggunakan npx untuk menjalankan server.
Bagaimana cara mengakses tools melalui URL alih-alih perintah lokal?
Tools ini dihosting melalui transport Streamable HTTP milik MCP oleh Cloudflare Worker, yang dapat Anda tambahkan sebagai custom connector di Claude.