Model Context Protocol (MCP) lets your coding assistant read Sportradar API Hub documentation and specifications from inside your IDE. For Engagement Tools (widgets), you can point the assistant at a resource-scoped MCP URL so Engagement Tools is the default context instead of browsing the entire Hub first.
This tutorial shows how to choose the right MCP URL, configure common assistants, and verify that the connection works.
Hub-wide MCP setup for all coding assistants is documented on the API Hub MCP page. This guide adds Engagement Tools–specific URL guidance and example prompts for widget integrators.
This tutorial is for engineers who integrate Sportradar Engagement Tools and want their AI assistant (Cursor, Claude Code, Codex, GitHub Copilot, OpenCode, or similar) to use official Engagement Tools docs while coding.
In this tutorial you will learn:
API Hub exposes a public MCP gateway. You can use it in two ways:
| Scope | URL | When to use |
|---|---|---|
| Entire API Hub | https://public.mcp.apidocs.sportradar.com/mcp | Discovering or comparing multiple Sportradar products |
| Engagement Tools (default context) | https://public.mcp.apidocs.sportradar.com/mcp?resource_slug=widgets | Integrating widgets, adapters, JWT, SIR, or other Engagement Tools docs |
Recommendation for this documentation set: use the Engagement Tools URL (resource_slug=widgets). The assistant still can reach the full gateway, but treats Engagement Tools as the default context.
This is the API Hub documentation MCP (public gateway on public.mcp.apidocs.sportradar.com). It is separate from product Marketplace MCP endpoints that require an API key (for example on developer.sportradar.com). Do not mix those configurations.
Use this URL in your assistant:
https://public.mcp.apidocs.sportradar.com/mcp?resource_slug=widgetsOn an Engagement Tools resource page in API Hub:
That copies the resource-scoped gateway URL for the page you are viewing (for Engagement Tools, equivalent to ?resource_slug=widgets).
Use the Engagement Tools MCP URL in your assistant’s MCP settings. Below, Cursor is shown end-to-end; other assistants use the same URL with that tool’s own MCP UI or config file. For assistant-specific installers and tabs (including one-click Install in Cursor), see the API Hub MCP setup page.
Ask your assistant something that should require Engagement Tools documentation. Prefer prompts that explicitly mention API Hub MCP so the model uses the connected tools.
Use Sportradar API Hub MCP to summarize how to get started with Engagement Tools widgets.Use Sportradar API Hub MCP to explain how JWT authentication works for Engagement Tools widgets.Use Sportradar API Hub MCP to find the SIR API methods used when adding and removing a widget.Use Sportradar API Hub MCP to outline how the odds adapter fits into a widget integration.Use Sportradar API Hub MCP to search Engagement Tools docs for onTrack / tracking guidance, then summarize the main integration steps.These match the suggestions on the API Hub MCP page:
What APIs are available in Sportradar API Hub?Use Sportradar API Hub MCP to list the APIs available in Sportradar API Hub.Use Sportradar API Hub MCP to find APIs related to live sports data.Use Sportradar API Hub MCP to find APIs related to fixtures, schedules, or results.Use Sportradar API Hub MCP to pick one public API and explain how a developer should start using it.| Symptom | What to check |
|---|---|
| Server missing or disconnected | Config file path, JSON syntax, reload/restart after save |
| Answers about unrelated Sportradar products | Prefer ?resource_slug=widgets so Engagement Tools is the default context |
| Auth / API key errors | Confirm you are using public.mcp.apidocs.sportradar.com, not a Marketplace MCP URL that expects x-api-key |
| Cannot find Copy MCP URL | Look in the resource page header actions, or construct the URL yourself (Option A) |
Resource-scoped gateways use the same public MCP base URL with ?resource_slug=<resource-slug> appended. Engagement Tools uses the resource slug widgets. See Scope to One Service on the API Hub MCP page.
Constructing the URL (Option A) works without using the UI. Prefer Option B when you want to confirm the slug matches the resource page you have open.
~/.cursor/mcp.json (user-wide), or a project-level .cursor/mcp.json if you prefer the server only for one repo.{
"mcpServers": {
"sr-api-hub-widgets": {
"url": "https://public.mcp.apidocs.sportradar.com/mcp?resource_slug=widgets"
}
}
}sr-api-hub-widgets appears as a connected MCP server in Cursor’s MCP settings.To use the full Hub instead of Engagement Tools as the default context, use server name sr-api-hub-public and URL https://public.mcp.apidocs.sportradar.com/mcp as shown on the API Hub MCP page.
If the assistant answers without citing API Hub tools, check that the MCP server is enabled, the URL includes resource_slug=widgets when you want Engagement Tools as the default context, and that you asked it to use API Hub MCP explicitly.