​

Sports MCP Server

This documentation covers the Gracenote Sports MCP Server, its public tool surface, its source-ownership model, and the recommended integration paths for MCP hosts and clients.

​

What This Docs Set Covers

​

Server responsibilities

• Read-only sports retrieval through MCP
• Public tool definitions and argument validation
• Bounded cross-source retrieval
• Deterministic envelopes with explicit partial, limitations, missingSections, and sources

​

Source ownership

• GSD Lookup for deep sports truth
• Dedicated availability contract for grounded where-to-watch flows
• On Programs for program-first sports context
• SportsEventCurrent only for freshness on already linked watch/program rows
• GSD Metadata for bounded enrichment

​

Common product jobs

• Resolve sports entities and IDs
• Browse league, team, and tour schedules
• Read standings, rankings, and event detail
• Ask where to watch a known game, event, or competition
• Build bounded competition hubs, series hubs, and event-center views

​

Start Here

​

Documentation Map

​

Getting started

• Access and API Keys
• Connect and Call Tools
• Quickstart

​

Core concepts

• Dual-Source Doctrine
• IDs, Crosswalks, and Bounded Windows
• Response Envelopes and Partials

​

Tool families

• Resolution and Scope Tools
• Deep Sports Truth Tools
• Program Connectivity and Watchability Tools
• Hybrid Bundle Tools
• Media and Assets Tools
• Tool Catalog

​

Prompt-to-tool mapping

• Prompt Library
• What Is On Today?
• Where Can I Watch This Game?
• What Does the League or Tournament Picture Look Like?

​

Current Surface

Sports MCP Server 1.4.1 exposes a 24-tool public catalog. The server remains stateless and read-only, and it does not turn itself into the host, client, or assistant layer. The host or client still owns:

• deciding which tool to call
• orchestration across multiple tool calls
• comparison logic
• permissions and review flow
• end-user wording and presentation