--- title: "API Hub MCP for AI Assistants" canonical_url: "https://apidocs.sportradar.com/resources/widgets/docs/tutorials/api-hub-mcp" markdown_url: "https://apidocs.sportradar.com/resources/widgets/docs/tutorials/api-hub-mcp.md" last_updated: "2026-08-12T08:29:08Z" --- # API Hub MCP for AI Assistants [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) 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. > **Info** > > Hub-wide MCP setup for all coding assistants is documented on the [API Hub MCP page](https://apidocs.sportradar.com/mcp). This guide adds Engagement Tools–specific URL guidance and example prompts for widget integrators. ## Intended Audience 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. ## Goals In this tutorial you will learn: - What the API Hub MCP gateway is and when to use a resource-scoped URL - How to obtain the Engagement Tools MCP URL - How to register that URL in your assistant - How to test the connection with Engagement Tools–focused prompts ## Prerequisites - An MCP-compatible coding assistant or IDE plugin - Permission to edit that assistant’s MCP configuration (user-level or project-level) - Optional: an API Hub account if you prefer to copy the URL from a resource page UI (not required if you construct the URL yourself) ## Choose Your MCP URL 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. > **Tip** > > Resource-scoped gateways use the same public MCP base URL with `?resource_slug=` appended. Engagement Tools uses the resource slug `widgets`. See [Scope to One Service](https://apidocs.sportradar.com/mcp#scope-to-one-service) on the API Hub MCP page. > **Warning** > > 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. ## Get the Engagement Tools MCP URL ### Option A — Construct the URL (no login) Use this URL in your assistant: ```text https://public.mcp.apidocs.sportradar.com/mcp?resource_slug=widgets ``` ### Option B — Copy from API Hub (UI) On an Engagement Tools resource page in [API Hub](https://apidocs.sportradar.com/): 1. Open the resource page (Engagement Tools / widgets). 2. In the **page header actions**, choose **Copy MCP URL**. That copies the resource-scoped gateway URL for the page you are viewing (for Engagement Tools, equivalent to `?resource_slug=widgets`). > **Tip** > > 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. ## Configure Your Assistant 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](https://apidocs.sportradar.com/mcp). **Cursor** 1. Prefer **Install in Cursor** on the [API Hub MCP page](https://apidocs.sportradar.com/mcp) if available, then change the URL to the Engagement Tools resource-scoped form below — **or** edit the config file manually. 2. Open or create `~/.cursor/mcp.json` (user-wide), or a project-level `.cursor/mcp.json` if you prefer the server only for one repo. 3. Add an MCP server entry that points at Engagement Tools: ```json { "mcpServers": { "sr-api-hub-widgets": { "url": "https://public.mcp.apidocs.sportradar.com/mcp?resource_slug=widgets" } } } ``` 4. Save the file and reload MCP servers in Cursor (or restart Cursor) so the new server is picked up. 5. Confirm `sr-api-hub-widgets` appears as a connected MCP server in Cursor’s MCP settings. > **Tip** > > 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](https://apidocs.sportradar.com/mcp). **Other Assistants** Supported assistants listed on the [API Hub MCP page](https://apidocs.sportradar.com/mcp) include **OpenCode**, **Claude Code**, **Codex**, and **GitHub Copilot**, in addition to Cursor. For each tool: 1. Open that assistant’s MCP / tools settings (or its documented config file), or use the installer tab on the API Hub MCP page. 2. Add a remote MCP server whose URL is: ```text https://public.mcp.apidocs.sportradar.com/mcp?resource_slug=widgets ``` 3. Give the server a clear name (for example `sr-api-hub-widgets`). 4. Reload or restart the assistant, then confirm the server is connected. Use the assistant tabs on [apidocs.sportradar.com/mcp](https://apidocs.sportradar.com/mcp) for the exact install path for your tool; replace the default Hub URL with the Engagement Tools URL above when you want Engagement Tools as the default context. ## Verify the Connection 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. ### Quick smoke test ```text Use Sportradar API Hub MCP to summarize how to get started with Engagement Tools widgets. ``` ### Engagement Tools–focused prompts ```text Use Sportradar API Hub MCP to explain how JWT authentication works for Engagement Tools widgets. ``` ```text Use Sportradar API Hub MCP to find the SIR API methods used when adding and removing a widget. ``` ```text Use Sportradar API Hub MCP to outline how the odds adapter fits into a widget integration. ``` ```text Use Sportradar API Hub MCP to search Engagement Tools docs for onTrack / tracking guidance, then summarize the main integration steps. ``` ### Hub-wide prompts (if you configured the unscoped gateway) These match the suggestions on the [API Hub MCP page](https://apidocs.sportradar.com/mcp): ```text What APIs are available in Sportradar API Hub? ``` ```text Use Sportradar API Hub MCP to list the APIs available in Sportradar API Hub. ``` ```text Use Sportradar API Hub MCP to find APIs related to live sports data. ``` ```text Use Sportradar API Hub MCP to find APIs related to fixtures, schedules, or results. ``` ```text Use Sportradar API Hub MCP to pick one public API and explain how a developer should start using it. ``` > **Tip** > > 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. ## Troubleshooting | 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) | ## Further Reading - [API Hub MCP setup](https://apidocs.sportradar.com/mcp) — gateway URL, assistant installers, and resource scoping - [Getting Started](https://apidocs.sportradar.com/resources/widgets/docs/tutorials/getting-started.md) — core Engagement Tools widget integration - [JSON Web Token (JWT)](https://apidocs.sportradar.com/resources/widgets/docs/tutorials/jwt.md) — auth for secure widget operations - [Global SIR API](https://apidocs.sportradar.com/resources/widgets/docs/tutorials/SIR.md) — widget loader and runtime API