Football Odds History vs Football Data
A side-by-side look at the Football Odds History and Football Data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Football Odds History for sports work as a local process; choose Football Data for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Football Odds History 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 Football Data when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_FOOTBALL_DATA_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 37/100 · Fair | 44/100 · Fair |
| 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 | PLATFORM_FOOTBALL_DATA_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Football Odds History | View Football Data |
Tools & capabilities
Football Odds History tools
No tool names declared yet. Check the project README from the listing page.
Football Data tools
No tool names declared yet. Check the project README from the listing page.
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.
Football Odds History
{
"mcpServers": {
"football-odds-history": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-football-odds-history"
]
}
}
}
Football Data
{
"mcpServers": {
"football-data": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-football-data"
],
"env": {
"PLATFORM_FOOTBALL_DATA_KEY": "YOUR_PLATFORM_FOOTBALL_DATA_KEY_HERE"
}
}
}
}
Frequently asked questions
Football Odds History is categorized under Sports and uses a local stdio subprocess. Football Data belongs to Sports and uses a local stdio subprocess. Pick Football Odds History for sports work and Football Data 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.
Football Odds History is listed as free. Auth: no auth required. Football Data 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 football-odds-history and football-data as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Football Odds History has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Football Data has 44/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.