Skip to main content
TheRundown provides a Model Context Protocol (MCP) server that lets AI assistants search our documentation directly. Ask questions about endpoints, query parameters, response fields, market IDs, billing headers, and integration patterns without leaving your editor.
This MCP server is documentation-only. It helps your assistant understand the API, but it does not stream live sports data or make authenticated API calls on your behalf. For live data, your agent still needs to call the real API using your own TheRundown key.
For authenticated sports and odds tools, use the separate data MCP with your own API key, hosted or local. The hosted, authenticated Streamable HTTP endpoint at https://mcp.therundown.io/mcp needs no install; the official public source repository and its versioned 0.2.3 source bundle run the local stdio server instead. Both expose the same six titled read-only tools — list_sports, list_affiliates, list_markets, list_events, get_main_lines, and list_futures — plus the therundown://brief resource carrying its scoped-data rules and first conversation. Initialization, metadata listings, and the exact brief read are keyless and do not call Product data; the six Product tools still require your key. Either way it is separate from this documentation server, which does not gain live-data tools when you install it. See the data MCP guide for auth headers and setup.

​
Server URL

​
Codex

Add the documentation server from your terminal:
This server searches TheRundown documentation only. It does not call the Product API or return live sports data. See OpenAI’s Codex MCP documentation for client configuration details.

​
Claude Code

Add the server from your terminal:

​
Cursor

Open the command palette and search “Open MCP settings”, then add to your mcp.json:

​
VS Code

Create or update .vscode/mcp.json in your project:

​
Claude Desktop

Add this to your Claude Desktop config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop after saving.

​
Windsurf

Add to your ~/.codeium/windsurf/mcp_config.json:

​
What you can ask

​
Connect the data MCP before a data request

The documentation MCP cannot execute Product API requests. First connect the data MCP with your own API key: the hosted endpoint needs no install, or run the local stdio server. Then use this conversation with the data MCP:
The best workflow is:
  1. Ask MCP which endpoint, filters, and market IDs you need
  2. Ask it for a code example in your language
  3. Have your agent call the real API with your own key
  4. Use the returned billing headers to keep usage under control
Once connected, you can ask your AI assistant questions like:
  • “What is the cheapest way to monitor NBA moneyline, spread, and total on DraftKings and FanDuel?”
  • “Should I use market delta or WebSocket for live line movement?”
  • “What headers tell me remaining data points on my key?”
  • “What are the market IDs for player props in NBA?”
  • “Show me a Python example for GET /api/v2/sports/{sportID}/events/{date} with market_ids and affiliate_ids filters”
  • “What does the 0.0001 sentinel value mean and how should I handle it?”
The MCP server searches across the API reference, guides, SDK docs, and reference tables to find relevant answers and examples.