TheRundown Data MCP server

Official TheRundown Data MCP

This is the official TheRundown source repository. aigeon-ai/therundown is unofficial.

A local, read-only Model Context Protocol server for TheRundown Product API. It fetches sports, affiliates, market definitions, events, futures, and open main lines using your own API key. It uses the official MCP SDK and Node.js 22+.

This directory is a runnable source example. The same six tools are also deployed as a hosted, authenticated Streamable HTTP endpoint at https://mcp.therundown.io/mcp; there is still no published npm package. The existing https://docs.therundown.io/mcp endpoint searches documentation only.

Cursor configuration for that server is in the Documentation MCP repository.

The separate HTTP adapter implements the hosted endpoint at https://mcp.therundown.io/mcp. It is excluded from the local ZIP and is never started by npm start; the ZIP remains a local, stdio-only install.

The checked-out source is version 0.2.3. Clients can initialize, list the six tools and public resources, and read therundown://brief before a Product API key is configured. Tool definitions now include human-readable titles and object-root output schemas. Product tool calls still require a key and fail before any network request when it is absent. The published source ZIP is version 0.2.3.

Download the versioned source bundle, verify its SHA-256 checksum, and extract it. The official ZIP is 41,072 bytes and its SHA-256 is cb0a0841aa040f049ffddec5b5fa2436cb9de721a30a3bd53270132db7204025. The ZIP manifest verifies every bundled source file. The ZIP README is generated from BUNDLE-README.md; this repository README also includes repository setup material. From the extracted ZIP directory:

npm ci --ignore-scripts
npm test

To run the checked-out source instead, use Node.js 22+ from this repository:

npm ci --ignore-scripts
npm test

For Claude Desktop's manual local configuration, add this to claudedesktopconfig.json where supported and restart the client. Use absolute Node 22+ and server paths; this source ZIP is not a .mcpb desktop extension:

{
  "mcpServers": {
    "therundown-data": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/therundown-data-mcp-0.2.3/server.mjs"],
      "env": { "THERUNDOWN_API_KEY": "YOUR_API_KEY" }
    }
  }
}

For Cursor, use the global ~/.cursor/mcp.json and make the key available in the environment that launches Cursor:

{
  "mcpServers": {
    "therundown-data": {
      "type": "stdio",
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/therundown-data-mcp-0.2.3/server.mjs"],
      "env": { "THERUNDOWN_API_KEY": "${env:THERUNDOWN_API_KEY}" }
    }
  }
}

Client references: local MCP servers, Cursor.

Replace the path and key locally. Use your client's secret storage or inherited environment when available. Do not commit a filled-in client config. The server reads THERUNDOWNAPIKEY from its process environment and sends it only as X-TheRundown-Key; keys are never accepted as tool arguments. stdout contains only MCP protocol messages. Without a key, the process stays available for MCP metadata discovery and returns a sanitized missing_credentials error for Product tool calls without making a network request.

The six tools are:

Shortened. The full README is on GitHub.