# OddsRelay [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/oddsrelay/oddsrelay-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/oddsrelay

## Description
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.

## Tools
Capabilities this server exposes over MCP:

- **sports** — none
- **events** — none
- **bookmakers** — none
- **coverage** — none
- **odds** — priced first, capped
- **event_odds** — priced first, capped
- **usage** — none

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "oddsrelay": {
    "command": "npx",
    "args": ["-y","oddsrelay-mcp"],
    "env": {
      "ODDSRELAY_KEY": ""
    }
  }
}
```

**Requires environment variables:** `ODDSRELAY_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the OddsRelay MCP server does

OddsRelay MCP server exposes read-only OddsRelay data to MCP-compatible AI assistants. It can list sports and competitions, retrieve events for a sport, identify bookmaker and exchange keys, and show coverage by product, bookmaker, and sport. It also provides odds data for matched boards and prices for an individual event.

The available bookmaker data includes UK and Irish bookmakers, including bet365, with exchange prices matched from Betfair, Smarkets, Matchbook, and BETDAQ where provided by OddsRelay. The server does not create, update, or delete data. It also does not read or write local files or contact hosts other than the OddsRelay API.

## How it works

The server runs as an MCP process over stdio and uses the `oddsrelay` TypeScript client to call `https://api.oddsrelay.io`. Authentication comes from the `ODDSRELAY_KEY` environment variable. The key is sent in the API authorization header, is not included in tool results or errors, and is not logged by the server.

Seven tools cover discovery, usage, and odds retrieval:

- `sports` returns paged sport and competition keys.
- `events` returns paged events and IDs for one sport.
- `bookmakers` lists bookmaker and exchange keys.
- `coverage` shows which bookmakers carry a sport on a product and exposes that product's market keys.
- `odds` reads a matched board for one sport and selected bookmakers.
- `event_odds` reads prices for one event across selected bookmakers and exchanges, with bookmaker and market filters.
- `usage` reports plan details, token balance, reset time, and key scope.

The `odds` and `event_odds` calls are quoted before execution. If the estimated cost exceeds `max_tokens`, the server makes no request that spends tokens and returns the price so the assistant can narrow its filters or raise the cap. Responses include the call cost and remaining balance. `limit` controls how many rows are returned, but reducing the row limit does not reduce the quoted cost.

## Setup and configuration

Create an API key through an OddsRelay account and provide it as `ODDSRELAY_KEY`. Node 18 or later is required for the npm-based setup routes. Claude Desktop users can instead install the `oddsrelay-mcp.mcpb` bundle from the latest GitHub release; the bundle includes its runtime and asks for the API key as a masked setting.

For Claude Code, add the server with the stdio transport and pass the environment variable:

```sh
claude mcp add --transport stdio oddsrelay --env ODDSRELAY_KEY=your_key_here -- npx -y oddsrelay-mcp
```

Claude Desktop configuration uses an `mcpServers` entry with `npx -y oddsrelay-mcp`, while Cursor accepts the same entry in `~/.cursor/mcp.json` for all projects or `.cursor/mcp.json` for one project. Cursor stores the key as plain text in that file, so keep it out of committed files.

## Tools and capabilities

OddsRelay MCP server is suited to workflows that first discover valid sport, event, bookmaker, and market keys, then request a narrowly filtered board or event. Long lists are limited by each tool's default or supplied `limit`; paged tools return a `next_cursor`, and truncated results report what remains through a `more` note. Invalid keys produce tool errors that can include accepted values.

Supported matched board types include `standard`, `2up`, `dutching`, `each-way`, `extra-place`, and `bog`. `event_odds` reads the raw board and therefore requires a key with permission to read raw odds.

## Limitations and notes

All operations are read-only, but the two odds tools are marked as cost-bearing calls because they spend API tokens. A client that asks for confirmation before such calls may prompt before every request. The token cap applies to the estimated request cost, and the default `max_tokens` value is small.

The server only supports the data and filters exposed by OddsRelay. It does not place bets, modify bookmaker accounts, persist files, or provide a separate local data store. API availability, returned markets, bookmaker coverage, and accepted keys come from OddsRelay. The project is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/oddsrelay/readme_