Nflverse vs FPL Context
A side-by-side look at the Nflverse and FPL Context MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NflverseSports · Local subprocess (stdio)nflverse — NFL play-by-play, player and team stats, schedules and injury41FairAuth: no auth requiredVerdict: choose Nflverse for sports work as a local process; choose FPL Context for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
NChoose Nflverse when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose FPL Context when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DATABASE_URL, DATABASE_ETL_URL, MCP_AUTH_TOKEN. - You want tools like
query_historical_stats, get_live_availability.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N Nflverse | |
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 41/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | DATABASE_URLDATABASE_ETL_URLMCP_AUTH_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Nflverse | View FPL Context |
Tools & capabilities
Nflverse tools
No tool names declared yet. Check the project README from the listing page.
FPL Context tools 2
query_historical_statsExecutes a read-only SQL `SELECT` against the historical stats database.get_live_availabilityCurrent FPL injury, suspension and availability flags, fetched live from the FPL API. Use it before recommending or captaining a player, so a newly flagged player isn't missed. It needs no database and no ingestion run.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Nflverse
{
"mcpServers": {
"nflverse": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nflverse"
]
}
}
}
FPL Context
{
"mcpServers": {
"fpl-context": {
"command": "uvx",
"args": [
"fpl-context-mcp"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE",
"DATABASE_ETL_URL": "YOUR_DATABASE_ETL_URL_HERE",
"MCP_AUTH_TOKEN": "YOUR_MCP_AUTH_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Nflverse is categorized under Sports and uses a local stdio subprocess. FPL Context belongs to Sports and uses a local stdio subprocess. Pick Nflverse for sports work and FPL Context for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Nflverse is listed as free. Auth: no auth required. FPL Context has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add nflverse and fpl-context as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nflverse has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. FPL Context has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.