Skip to content

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.

  1. Exchange your Sports API client_id and secret (secret_key or JSON alias client_secret) once over HTTPS (POST /api/v1/token on the MCP host) from your backend, CI, or a secure shell (curl is fine). See Get a PAT. Never embed the secret in mcp.json or static docs.
  2. Store the returned Personal Access Token (PAT) and send it on every MCP request: Authorization: Bearer <PAT>.
  3. 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.

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.

TopicOn this portalIn statscore-mcp
Mint a PAT, errors, rate limitsGet a PAT-
Headers, entitlements, troubleshootingConnect a clientExtra client setups (stdio proxies, OS-specific paths)
Sports API behaviourRecipes, Concepts-
Gateway internals-Repository docs/

https://mcp.statscore.com/mcp

This is the production MCP gateway on the public developer portal.

PageContent
Get a PATPOST /api/v1/token, errors, rate limits
Connect a clientCursor, supergateway, headers, troubleshooting

More connection examples: statscore/statscore-mcp docs.

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).