Who This Is For
- AI product teams evaluating a sports data platform for customer-facing experiences
- developers wiring an MCP host, agent framework, orchestration layer, or backend
- product, operations, support, finance, and procurement-adjacent stakeholders who need to understand the product without reading code
Why Teams Buy Sports MCP Server Instead of Raw Sports APIs
| If you start from raw sports APIs | If you start from Sports MCP Server |
|---|---|
| you design your own orchestration layer before you can ship | you evaluate one AI-ready interface from day one |
| you resolve fuzzy names and IDs yourself | you use discovery and resolution tools built for LLM workflows |
| you stitch schedules, standings, match detail, and history manually | you choose between atomic tools and bundled product-ready calls |
| you bolt on governance later | you get product-scoped keys, usage controls, exports, and billing in the portal |
| your team debates data hierarchy before it can build | your team starts from user jobs like scoreboards, match centers, season hubs, and watchability |
What You Can Ship
| Experience | What Sports MCP Server gives you |
|---|---|
| Live scoreboards | current schedules, results, and compact dayboard bundles |
| Match centers | one-call or tactical match views with actions, lineups, stats, and optional odds |
| Team and player hubs | canonical profiles, rosters, schedules, and season stats |
| League hubs | standings, structure, brackets, teams, classifications, and tiers |
| Watchability assistants | linkage between sports entities and broadcast programs |
| Historical products | season snapshots, year-over-year comparison, and series championship context |
What You Get On Day One
- a hosted Sports MCP endpoint over HTTP
58production tools across discovery, live, season, historic, and watchability jobs- a customer portal for entitlement, API keys, usage, alerts, extra usage, exports, users, and billing
- canonical Gracenote IDs that are reusable across prompts, tools, and product surfaces
How To Evaluate In One Afternoon
- Confirm your org has access in the customer portal.
- Create a product-scoped API key in
API. - Run Quickstart and make your first
tools/listandtools/call. - Choose one use case and prove end-to-end value with a real product workflow.
Sports Terms Your Team Should Know
| Term | Plain-English meaning |
|---|---|
sport | the top-level category, such as soccer, tennis, basketball, or motorsport |
league | a competition customers usually think of as a league or tournament, such as Premier League or NBA |
series | a championship or umbrella competition spanning multiple leagues, common in motorsport and similar structures |
season | a time-bounded campaign for a league or series |
match | one scheduled or completed contest |
participant | a team or person involved in that competition context |
standings | the ranked table for a competition, optionally filtered by conference, division, or tier |
watchability | the linkage between a sports entity and related program or broadcast metadata |
Product Surfaces
| Surface | URL | What it is for |
|---|---|---|
| Documentation | https://docs.etonecarg.com/customer | evaluation, onboarding, implementation, and operations |
| Customer portal | https://dash.etonecarg.com/products/sports-mcp-server | entitlement, API keys, usage, billing, exports, and users |
| Sports MCP endpoint | https://sports-mcp-server.etonecarg.com/ | MCP hosts, agent backends, and direct integrations |
Start Here
- Use Quickstart if you already have a key and want a working call in minutes.
- Use Development if you are designing the production integration.
- Use Customer Portal if you are setting up access and operating the product.
- Use Use Cases if you want to evaluate the platform by what you can ship.
- Use Reference if you already know you need low-level MCP and tool details.