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

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.

Gateway URL

Production:

https://mcp.statscore.com/mcp

Pre-production (when provided on your contract):

https://mcp.statscore.dev/mcp

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

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