Bietet einem AI-Client Live-NFL-Fantasy-Football-Analysen, einschließlich Spielerstatistiken, Dynasty-Werten, Sleeper-League-Daten und benutzerdefinierten Excel-Prognosen.
Auch bekannt als dachhack/stathead
- Stars
- 3
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 1.0.126
- Letzter Commit
- 15. Nov. 2026
- Lizenz
- MIT
Was ist StatHead MCP?
StatHead ist ein MCP server. Bietet einem AI-Client Live-NFL-Fantasy-Football-Analysen, einschließlich Spielerstatistiken, Dynasty-Werten, Sleeper-League-Daten und benutzerdefinierten Excel-Prognosen.
Zusammenfassung generiert aus dem README des Projekts
Über StatHead MCP server
Fantasy-Football-Enthusiasten und Analysten können direkt über AI-Clients wie Claude Desktop, Cursor oder Claude Code auf Live-NFL-Daten und Dynasty-Werte zugreifen. Dieser Server bietet über 50 Tools, die alles abdecken – von Spielerstatistiken der Saison und Snap Counts bis hin zu fortgeschrittenen Next Gen Stats und Injury Reports. Er lässt sich tief in Sleeper-Leagues integrieren, sodass Nutzer Tabellen, Rosters, Transaktionen und sogar das Manager-Exposure über verschiedene Ligen hinweg einsehen können.
Nutzer können ihre eigenen benutzerdefinierten Rankings und Prognosen verwalten, indem sie Daten nach Excel exportieren, manuelle Änderungen vornehmen und die Dateien wieder importieren, um die internen Modelle des Servers zu überschreiben. Das Setup ist unkompliziert: Entweder via npx für die lokale Ausführung über stdio oder als Remote-Connector über eine gehostete URL. Während die meisten Daten aus Open-Upstreams wie nflverse und Sleeper stammen, erfordern spezifische Features wie Betting Odds einen externen API-Key.
Was du damit machen kannst
- 1Sleeper League-Aktivitäten analysierenBitte die KI, aktuelle Trades und Waiver-Wire-Moves innerhalb einer bestimmten Sleeper-League zu überprüfen.
- 2Dynasty-Trade-Werte bewertenErmittle den fairen Marktwert eines Spielers anhand historischer Sleeper-Trade-Daten und zukünftiger Prognosen.
- 3Wöchentliche Matchup-Schwierigkeit einschätzenIdentifiziere, welche Spieler basierend auf den zugelassenen Defensive Points die einfachsten kommenden Spielpläne haben.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du StatHead MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenStatHead MCP in Claude Code installieren
$ claude mcp add stathead-mcp -- npx -y stathead-mcpStatHead MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"stathead-mcp": {
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}StatHead MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"stathead-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}StatHead MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"stathead-mcp","type":"stdio","command":"npx","args":["-y","stathead-mcp"]}'StatHead MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"stathead-mcp": {
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}StatHead MCP in Codex installieren
$ codex mcp add stathead-mcp -- npx -y stathead-mcpStatHead MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.stathead-mcp] command = "npx" args = ["-y", "stathead-mcp"]
StatHead MCP in Gemini CLI installieren
$ gemini mcp add -s user stathead-mcp npx -- -y stathead-mcpStatHead MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"stathead-mcp": {
"command": "npx",
"args": [
"-y",
"stathead-mcp"
]
}
}
}Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbardachhack/stathead is public and reachablegithub.com/dachhack/stathead ↗Bestanden
- Paket nennt dieses Repository als Quellestathead-mcp names dachhack/stathead as sourcenpmjs.com/package/stathead-mcp ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for stathead-mcpnpmjs.com/package/stathead-mcp/v/1.0.126#provenance ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-12github.com/dachhack/stathead ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from stathead-mcpBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten1 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehenstathead-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.
StatHead MCP Fragen
Wie füge ich StatHead MCP zu Claude Code hinzu?
Führe claude mcp add stathead-mcp -- npx -y stathead-mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich StatHead MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie kann ich meine eigenen Prognosen und Rankings nutzen?
Du kannst Prognosen oder Rankings in eine Excel-Datei exportieren, die Werte in Excel oder Google Sheets bearbeiten und die Datei anschließend wieder importieren, um diese Werte als Overrides in deinen Abfragen zu verwenden.
Benötigt dieser Server Laufzeitabhängigkeiten?
Nein, es handelt sich um ein einzelnes, in sich geschlossenes Bundle ohne Laufzeitabhängigkeiten, das alle Daten bei Bedarf abruft.
Kann ich dies mit Claude Desktop nutzen?
Ja, du kannst ihn über npx zu deiner Claude Desktop Konfigurationsdatei hinzufügen, um den Server auszuführen.
Wie kann ich auf die Tools über eine URL statt über einen lokalen Befehl zugreifen?
Die Tools werden über den Streamable HTTP Transport von MCP durch einen Cloudflare Worker gehostet, den du als Custom Connector in Claude hinzufügen kannst.