Skip to content

TutorialsLesson 13 of 15Products7 min read

Connecting AI clients with the Enterprise MCP server

Connect a compatible AI client to the RacingAPI.net Enterprise MCP server through OAuth consent or an API-key header, and understand limits and safety.

  • Know when MCP fits and when REST is better
  • Connect via OAuth or an API-key header
  • Keep usage inside Enterprise limits

What MCP is here

The Model Context Protocol lets a compatible AI client call tools on a server. RacingAPI.net offers a read-only MCP server at https://racingapi.net/api/mcp for Enterprise plans only. It uses POST, not the REST GET endpoints, and exposes the same racing feeds as tools: racecards, results, horses, connections, courses, weather, odds and saved tips. Developer and Professional plans include REST access but not MCP.

MCP suits analysis inside an AI assistant. It is not the right tool for powering a public website: use REST from your server for that. And it is distinct from the support chat on this website, which answers account questions and does not use your racing feeds.

Two ways to connect

DiagramOAuth consent connection
OAuth consent connection: step 1, Add the server URL; step 2, Sign in and consent; step 3, Tools available; step 4, Revoke any time.1 VISITORAdd the server URL2 YOUR SERVERSign in and consent3 RACINGAPI.NETTools available4 STOPRevoke any time
  1. 1Add the server URL. In your AI client, add https://racingapi.net/api/mcp.
  2. 2Sign in and consent. Approve read-only racing access on the RacingAPI.net consent screen.
  3. 3Tools available. The client calls tools; each call is checked against Enterprise access.
  4. 4Revoke any time. Dashboard, Connect AI lists connections you can revoke.
The client never sees your REST key when you use consent.

Developer clients that support custom headers can authenticate with an API key instead, sending X-API-Key or a bearer header. Keep that key in the client's secure configuration, never in a shared prompt or chat transcript.

{
  "mcpServers": {
    "racingapi": {
      "url": "https://racingapi.net/api/mcp",
      "headers": { "X-API-Key": "SET_FROM_YOUR_SECRET_STORE" }
    }
  }
}
Example configuration for a client that supports remote MCP with headers

Limits and good habits

  • Racing tool invocations share Enterprise's per-second limit and unlimited monthly allowance with REST traffic. Protocol discovery is not itself a racing-data request.
  • Ask specific questions with a course or date; broad prompts make clients call many tools.
  • AI-provider fees, where your client charges them, are separate from RacingAPI.net.
  • 403 means Enterprise access is missing, the account is suspended or the origin is untrusted. Fix the cause rather than retrying.

Tool names, arguments and client-specific steps are in the MCP guide. Product overview: Horse Racing MCP Server.

Reference material

Exact schemas: API reference. First call: Quickstart. Copy-ready helpers: Code examples. Plans: Pricing.