Connect a client
Required headers
Section titled “Required headers”Every call to the MCP gateway should include:
| Header | Value |
|---|---|
| Authorization | Bearer <YOUR_PAT> |
| Accept | application/json, text/event-stream |
| Content-Type | application/json |
If you see 406 (Client must accept text/event-stream), add Accept explicitly in Cursor headers.
Obtain YOUR_PAT via token exchange; do not paste secret_key here.
Cursor (Streamable HTTP)
Section titled “Cursor (Streamable HTTP)”Settings → MCP, or ~/.cursor/mcp.json / project .cursor/mcp.json:
{ "mcpServers": { "statscore-mcp": { "url": "https://mcp.statscore.com/mcp", "headers": { "Authorization": "Bearer YOUR_PAT", "Accept": "application/json, text/event-stream" } } }}Replace YOUR_PAT. Restart Cursor or reload MCP after saving.
Claude Desktop, Antigravity, stdio-only clients
Section titled “Claude Desktop, Antigravity, stdio-only clients”Many clients do not speak Streamable HTTP natively. Use a local proxy such as
supergateway with --streamableHttp and
--header "Authorization: Bearer YOUR_PAT".
Full matrix (Windows paths, npx, Python proxy): see
MCP client connection in the statscore-mcp repository.
Tool overview (production)
Section titled “Tool overview (production)”After connect, the client lists tools such as:
| Tool | Purpose |
|---|---|
sports_api_get_events | Matches / events |
sports_api_get_standings | League tables |
sports_api_get_h2h | Head-to-head |
sports_api_get_lineups | Lineups |
sports_api_get_participants | Teams / athletes |
sports_api_get_usage | Usage telemetry |
Parameters match Sports API concepts (sport_id, season_id, etc.). Tool names and availability
can change between gateway releases - after connect, your MCP client's tool list is the source of
truth, not a static table in these docs.
Troubleshooting
Section titled “Troubleshooting”| Symptom | What to check |
|---|---|
401 on /mcp | PAT missing, wrong, or revoked |
| 403 on data | Valid PAT but missing contract entitlement - see below |
| 406 | Add Accept header (see above) |
| 429 | Rate limit on /mcp or on token exchange |
502 on POST /api/v1/token | STATSCORE OAuth unreachable; retry, see Get a PAT |
| Client timeout on bare URL | Use supergateway for non-HTTP-native clients |
403 on tool calls (entitlements)
Section titled “403 on tool calls (entitlements)”A 403 with a valid PAT (no 401) usually means the underlying Sports API would also refuse that data for your account. MCP tools mirror REST access: competitions, seasons, and feeds you have not licensed are not returned, even when authentication succeeds.
- Retry the same question with a REST access token from Get a token. If REST returns forbidden or empty where you expect data, the limit is contractual, not MCP-specific.
- To extend coverage, contact STATSCORE support or your account manager.