Api Football vs Betsapi
A side-by-side look at the Api Football and Betsapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Api Football for sports work as a local process; choose Betsapi 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 Api Football when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
fixtures, standings, team_search.
Choose Betsapi when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
betsapi_inplay, betsapi_upcoming, betsapi_event_odds.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 56/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | 3 |
| Full listing | View Api Football | View Betsapi |
Tools & capabilities
Api Football tools 9
fixturesGet match fixtures (upcoming + recent) by league, team, or date. Use league=1 for FIFA World Cup, league=39 for EPL, league=140 for La Liga. Returns kickoff, teams, score (if played), venue, status.standingsCurrent standings table for a league. Returns rank, team, points, goal difference, form. Use league=1 for World Cup.team_searchLook up a team by name + country to get its team_id for use in other tools.league_searchLook up a league/tournament/competition by name to get its league_id.predictionsAPI-Football's own match-outcome predictions. Returns home/draw/away win probabilities, advice, h2h context, form. Use for "who will win" research on specific fixtures.football_injuriesCurrently injured and unavailable football players for a club or a league — who is out, the injury or reason, and whether they are ruled out or merely doubtful. Covers Serie A, the Premier League, La Liga, the Bundesliga, Ligue 1 and other competitions worldwide. Use for questions about which playe…football_squadThe current player squad for a football club — every player with shirt number, position, age and nationality. Use for questions about who plays for a club, squad lists, and a team roster.h2hHead-to-head record between two teams. Returns last N matches with scores.api_football_statusAPI-Football account status for the key in use: subscription plan name, whether it is active and when it ends, requests used today against the daily limit, and the per-minute limit the vendor reports in its rate-limit headers. The vendor does not count this call against the quota. Use it to tell a…
Betsapi tools 3
betsapi_inplayLive in-play sport matches happening right now, with running score and match clock. Pass a sport_id (${SPORT_IDS}). Example: betsapi_inplay({ sport_id: "1", _apiKey: "your-key" })betsapi_upcomingUpcoming (scheduled) sport events for a sport, optionally for a given day. Pass a sport_id (${SPORT_IDS}) and optionally day=YYYYMMDD. Example: betsapi_upcoming({ sport_id: "1", day: "20260704", _apiKey: "your-key" })betsapi_event_oddsBookmaker odds for a single event across markets (moneyline, spreads, totals). Odds are deeply nested by market, so the full structure is returned under `raw`. Get an event_id from betsapi_inplay or betsapi_upcoming first. Example: betsapi_event_odds({ event_id: "12345678", _apiKey: "your-key" })
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.
Api Football
{
"mcpServers": {
"api-football": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-api-football"
]
}
}
}
Betsapi
{
"mcpServers": {
"betsapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-betsapi"
]
}
}
}
Frequently asked questions
Api Football is categorized under Sports and uses a local stdio subprocess. Betsapi belongs to Sports and uses a local stdio subprocess. Pick Api Football for sports work and Betsapi 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.
Api Football is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Betsapi is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 api-football and betsapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Api Football has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Betsapi has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.