OddsRelay vs TheRundown Data MCP

A side-by-side look at the OddsRelay and TheRundown Data MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

OddsRelay logoOddsRelaySports · Local subprocess (stdio)Read-only access to OddsRelay odds data for AI assistants: pre-match odds from UK and Irish bookmakers, bet365 included, matched to Betfair, Smarkets, Matchbook and BETDAQ lay prices, plus sport, event, bookmaker and coverage lists. The two tools that spend tokens ask for a quote first and refuse any call above the max_tokens cap you set.61GoodAuth: api key requiredTheRundown Data MCP logoTheRundown Data MCPSports · Remote HTTP/SSERead-only TheRundown sports odds/events via six authenticated Product API tools; API key required.40FairAuth: not declared

Verdict: choose OddsRelay for sports work as a local process; choose TheRundown Data MCP for sports over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

OddsRelay logoChoose OddsRelay when

  • You need dedicated capabilities in the Sports domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: ODDSRELAY_KEY.
  • You want tools like sports, events, bookmakers.
Explore OddsRelay

TheRundown Data MCP logoChoose TheRundown Data MCP when

  • You need dedicated capabilities in the Sports domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: THERUNDOWN_API_KEY.
Explore TheRundown Data MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOddsRelay logoOddsRelayTheRundown Data MCP logoTheRundown Data MCP
CategorySportsSports
Quality signal61/100 · Good40/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsODDSRELAY_KEYTHERUNDOWN_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools7Not listed

Tools & capabilities

OddsRelay tools 7

  • sportsLists sport and competition keys (such as soccer or soccer_epl) for the sport filter of odds and events. Costs no tokens. Paged: pass next_cursor back as cursor.
  • eventsLists the events of one sport with their ids, for event_odds. Costs no tokens. Paged: pass next_cursor back as cursor.
  • bookmakersLists the bookmaker and exchange keys that odds, event_odds and coverage take. Costs no tokens.
  • coverageShows which bookmakers carry which sports on one product, and that product's market keys (the values odds takes as markets). Filter by bookmaker or sport. Costs no tokens and sends no key.
  • oddsReads a matched board (bookmaker back prices with exchange lay prices) for one sport at the bookmakers you name. Spends tokens: priced first, and refused when it would cost more than max_tokens.
  • event_oddsReads one event's prices (id from events or odds) at each bookmaker and exchange carrying it, narrowed to the bookmakers and markets you name. Needs a key that can read raw odds. Spends tokens: priced first, and refused when it would cost more than max_tokens.
  • usageShows this key's plan, token balance, reset time and scope. Costs no tokens.

TheRundown Data MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

OddsRelay

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "oddsrelay": {
      "command": "npx",
      "args": [
        "-y",
        "oddsrelay-mcp"
      ],
      "env": {
        "ODDSRELAY_KEY": "YOUR_ODDSRELAY_KEY_HERE"
      }
    }
  }
}

TheRundown Data MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "therundown-data-mcp": {
      "url": "https://mcp.therundown.io/oauth/mcp"
    }
  }
}

Frequently asked questions

OddsRelay is categorized under Sports and uses a local stdio subprocess. TheRundown Data MCP belongs to Sports and uses a remote HTTP/SSE transport. Pick OddsRelay for sports work and TheRundown Data MCP for sports.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

OddsRelay is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. TheRundown Data MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add oddsrelay and therundown-data-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, OddsRelay has a quality signal of 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars. TheRundown Data MCP has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.