MCP · Enabled per account

Football data inside your AI assistant.

The FootballAPI.net MCP server lets compatible AI clients call qualified football feeds, read-only. The REST API does not need MCP.

https://footballapi.net/api/mcp

What it is

MCP (Model Context Protocol) is an open standard that lets AI clients call external tools. Every tool call retrieves supplied football data. It is separate from the documentation assistant on this site.

Transport: stateless Streamable HTTP, POST with JSON responses.
Read-only. No account, key or billing access.
Tools return supplied data. They do not predict results or give betting advice.

Eligibility

MCP requires active Pro-plan API access with MCP enabled for your account. Tool calls share the account's 250,000 included successful requests per UTC day; additional successful requests on a metered subscription cost €0.002 each on the monthly EUR invoice. Protocol discovery does not consume feed usage. Manage connections in Dashboard, Connect AI.

Connect a client

Browser sign-in (OAuth)

Add a custom connector with the server URL. The client opens FootballAPI.net; sign in, review the consent screen, choose an active key and approve. Client support varies.

Key header

Send an existing API key as X-API-Key. Keys are created in API keys.

{
  "mcpServers": {
    "footballapi": {
      "url": "https://footballapi.net/api/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}

OAuth details

Item	Value
Flow	OAuth 2.1 authorization code with PKCE (S256)
Access	Read-only football data
Approval	Explicit consent on FootballAPI.net. Never automatic.

OAuth tokens are not REST keys

Access tokens only work on the MCP server. Use API keys for REST requests.

Tools

Planned tool catalogue; the server's tools/list is authoritative.

Tool	Description	REST equivalent
`list_feeds`	Football feeds in the public catalogue with their parameters.	`/api/football/catalogue`
`get_scores`	Today's matches by competition, with status strings as supplied.	`/api/v1/football/{feedId}`
`get_fixtures`	Season fixtures for one competition by leagueId.	`/api/v1/football/{feedId}`
`get_standings`	League table for one competition by leagueId.	`/api/v1/football/{feedId}`
`get_team`	Team profile, squad and venue by teamId.	`/api/v1/football/{feedId}`
`get_player`	Player profile and career sections by playerId.	`/api/v1/football/{feedId}`
`get_head_to_head`	Historical meetings between two teams.	`/api/v1/football/{feedId}`
`get_leaderboards`	Top scorers, assists and cards for a competition.	`/api/v1/football/{feedId}`

Raw protocol

Protocol version 2025-03-26. Replace the placeholder with an OAuth token, or send X-API-Key.

curl -s https://footballapi.net/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1"}}}'

Usage and limits

Feed-retrieving tool calls count against the same limits as your REST requests. The handshake and tool discovery do not count as feed usage.

Errors

Situation	Response
Missing, expired or revoked token or key	HTTP 401
MCP not enabled or access inactive	HTTP 403
Rate limit exceeded	Tool error with `retryAfter`
Feed returned nothing	Tool result says nothing was supplied. Nothing is invented.

Privacy and revocation

The AI client you choose receives the data it retrieves under its own terms.
Revoke an OAuth connection in Connect AI, or revoke the linked key.