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.
list_sports, list_affiliates, list_markets, list_events, get_main_lines, and list_futures. The local server also exposes therundown://brief for its scoped-data rules and first conversation. It is separate from this documentation server, which does not gain live-data tools when you install it. A hosted data MCP is not currently available.
Server URL
Codex
Add the documentation server from your terminal:Claude Code
Add the server from your terminal:Cursor
Open the command palette and search “Open MCP settings”, then add to yourmcp.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
Windsurf
Add to your~/.codeium/windsurf/mcp_config.json:
What you can ask
Prepare the local data MCP before a data request
The documentation MCP cannot execute Product API requests. First install and connect the local data MCP scaffold with your own API key. Then use this conversation with the local data MCP:- Ask MCP which endpoint, filters, and market IDs you need
- Ask it for a code example in your language
- Have your agent call the real API with your own key
- Use the returned billing headers to keep usage under control
- “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}withmarket_idsandaffiliate_idsfilters” - “What does the
0.0001sentinel value mean and how should I handle it?”