Nflverse

What Nflverse does

Nflverse MCP server provides agent-accessible NFL data compiled by the nflverse project. Its coverage includes play-by-play records, player season totals, team game logs, schedules, game results, betting lines, and weekly injury reports. Most football data reaches back to the 1999 season; injury reports begin in 2009.

The server is listed in the 🏃 Sports category and fits applications that need structured NFL information rather than general web search. Possible uses include comparing player production, reviewing a team’s season, inspecting individual games, checking schedule context, or finding injury-report status for a player or team.

How it works

Nflverse MCP server reads published nflverse season files when a request is made. The response includes data_as_of, identifying the source file’s last-modified time, together with source and licence metadata. Current-season files may change as nflverse refreshes them during the season.

A hosted connection is available at https://gateway.pipeworx.io/nflverse/mcp. The endpoint also exposes shared Pipeworx gateway tools, including routing and discovery tools, so its tools/list result contains more than the NFL-specific tools. The standalone npm package exposes only the Nflverse tools over stdin and stdout.

Requests that match no records return found: false and a message. Invalid team codes or malformed game IDs produce errors that identify accepted formats. Play-by-play requests are filtered to one game while the source table is streamed, rather than returning an entire season.

Setup and configuration

No API key or environment variable is required. For an MCP client that supports streamable HTTP, add the hosted URL as an MCP server. The README specifically documents Claude Desktop, Cursor, and Windsurf configurations.

For local stdio operation, run npx -y @pipeworx/mcp-nflverse or configure an MCP client with that command and package argument. This mode does not require a Pipeworx account or gateway round trip. The same data and NFL tools are available, but shared gateway meta-tools are not.

The tools can also be called over HTTP. For example, the gateway exposes /v1/tools/nfl_player_season_stats, and tool schemas can be inspected through the corresponding /v1/tools/ endpoint.

Tools and capabilities

• nfl_player_season_stats returns one player’s season totals across passing, rushing, receiving, defense, kicking, returns, EPA, CPOE, target share, and fantasy points. Names and nflverse or GSIS IDs are accepted.
• nfl_team_game_log returns a team’s games for one season, including opponent, location, score, result, and multiple statistical totals.
• nfl_play_by_play retrieves plays from one game, with optional quarter, play-type, and result-limit filters. Records can include down, distance, field position, players, descriptions, yards, score, EPA, and win probability.
• nfl_schedule returns season games with dates, kickoff information, scores, overtime, closing spread and total, venue details, weather, starting quarterbacks, coaches, and referee data.
• nfl_injuries returns weekly official injury-report entries with practice participation and game status, optionally filtered by season, team, week, or player.

Limitations and notes

Team codes follow nflverse conventions. For example, LA is the primary Rams code and LAR is accepted as an alias; historical seasons may use OAK, SD, or STL. A season spans September through the following February, so playoff games played in the next calendar year remain part of the preceding season.

Play-by-play is comparatively large, at about 19 MB compressed and 100 MB as CSV per season. The server streams and filters it to the requested game. The nflverse-data source is licensed CC-BY-4.0, requiring attribution; the package itself is licensed MIT. The integration is independent and unofficial, and is not affiliated with the upstream provider.