SportQuanta exposes its agent tools over MCP Streamable HTTP. The customer endpoint uses the same workspace API token as the REST API, and MCP calls draw from the same organization quota.
MCP access is included with Sharp and Max. Core and self-serve trials can browse the tool reference but cannot open an MCP session.

​
Connect

Create an API token in the SportQuanta dashboard, then configure your MCP client with the endpoint and bearer token shown on the dashboard’s MCP server page. Tokens are displayed only once when created. The customer endpoint uses Streamable HTTP and requires:
The MCP client performs the standard initialize handshake. SportQuanta then authenticates the token, checks the organization’s effective MCP entitlement, and opens a metered session.

​
Tool discovery

MCP clients discover the exact active schema through tools/list. The Agent tool reference groups the current surface by sport and explains when to use each family. Discovery operations do not consume quota. Data-reading tool calls consume the same organization allowance used by REST requests.

​
Security

  • Use a dedicated workspace API token for each integration.
  • Never put a token in source control or client-side application code.
  • Revoke a token from the dashboard when an integration is retired.
  • A revoked token cannot open a new session; active lease staleness is bounded by the server’s short lease lifetime.

​
Errors