MCP server for AI agents
The STATSCORE MCP gateway exposes the same sports data as the REST API as read-only tools an AI client can call from a conversation: schedules, results, standings, lineups, H2H, and more.
How authentication works
Section titled “How authentication works”- Exchange your Sports API
client_idand secret (secret_keyor JSON aliasclient_secret) once over HTTPS (POST /api/v1/tokenon the MCP host) from your backend, CI, or a secure shell (curlis fine). See Get a PAT. Never embed the secret inmcp.jsonor static docs. - Store the returned Personal Access Token (PAT) and send it on every MCP request:
Authorization: Bearer <PAT>. - Configure your MCP client with the gateway URL and the PAT in headers (see Connect a client).
Revoked or invalid PATs receive 401 on /mcp.
PAT vs REST access token
Section titled “PAT vs REST access token”The PAT from POST /api/v1/token on the MCP host authorizes /mcp tool calls only.
The short-lived access token from the Sports API OAuth flow in
Get a token authorizes api-media.statscore.com REST calls.
Same account credentials at exchange time, two different tokens for two surfaces - do not put the REST
token in MCP Authorization or the PAT on REST URLs.
Where to read more
Section titled “Where to read more”| Topic | On this portal | In statscore-mcp |
|---|---|---|
| Mint a PAT, errors, rate limits | Get a PAT | - |
| Headers, entitlements, troubleshooting | Connect a client | Extra client setups (stdio proxies, OS-specific paths) |
| Sports API behaviour | Recipes, Concepts | - |
| Gateway internals | - | Repository docs/ |
Gateway URL
Section titled “Gateway URL”https://mcp.statscore.com/mcp
This is the production MCP gateway on the public developer portal.
Next steps
Section titled “Next steps”| Page | Content |
|---|---|
| Get a PAT | POST /api/v1/token, errors, rate limits |
| Connect a client | Cursor, supergateway, headers, troubleshooting |
More connection examples: statscore/statscore-mcp docs.
Read-only tools
Section titled “Read-only tools”MCP tools do not modify bookings, webhooks, or account data. They mirror GET-style Sports API access
for agent workflows. Tool names on production follow the sports_api_* prefix (see your client after connect).