# odds-api.net MCP Server [Verified owner] [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/odds-api/odds-api  
**GitHub Stars:** 39  
**npm Downloads (last month):** 91  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/odds-api-net-mcp-server

## Description
MCP tools for sports and racing odds, bookmaker comparison, line movement, results, and betting research using the Odds API.

## Claude Desktop Quick Installation
Install path inferred — verify against the README before running it. Uses `npx` (confidence: medium):

```json
"mcpServers": {
  "odds-api-net-mcp-server": {
    "command": "npx",
    "args": ["-y","@odds-api/mcp"],
    "env": {
      "ODDS_API_KEY": ""
    }
  }
}
```

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

## Documentation

## What odds-api.net MCP Server does

The odds-api.net MCP Server exposes the Odds API to MCP-compatible coding agents. It focuses on sports and racing data, including events, bookmaker prices, results, and market research. Agents can use it to search for events and odds, compare prices across bookmakers, inspect line movement, and investigate potential betting opportunities.

The server is part of a broader OpenAPI-first API project. The same service also provides REST endpoints, TypeScript and Python SDKs, an OpenAPI contract, and examples for arbitrage, positive expected value, bookmaker comparison, and line movement. The MCP interface is the option intended for coding agents that need to work with the service through agent tools rather than direct HTTP calls.

## How it works

The MCP server acts as an agent-facing layer over the Odds API. An MCP-compatible client invokes tools for sports and racing queries, while the underlying API supplies the returned market data. The available service includes endpoints for discovering sports, leagues, coverage, events, odds, and results.

Coverage is not static: leagues, bookmakers, and markets may be added or retired. Production workflows can use the API’s coverage discovery endpoints to determine what is currently available instead of relying on a fixed list. The service also includes Betfair exchange data, including order book snapshots and live-market access through the API’s exchange endpoints.

## Setup and configuration

An Odds API key is required. The API key can be obtained from [odds-api.net](https://odds-api.net) and is represented by the `ODDS_API_KEY` environment variable in the project’s examples. The underlying REST API uses the `X-API-Key` request header for authentication.

The default API base URL is `https://api.odds-api.net/v1`. Set `ODDS_API_BASE_URL` when a different API base is needed. For local demonstrations and tests, `ODDS_API_MOCK=1` enables the project’s mock mode, allowing examples to run without a live API key. The project also provides a coverage page and a `GET /v1/coverage` endpoint for discovering current availability.

## Tools and capabilities

The MCP toolset supports workflows such as:

- Searching sports events and retrieving odds.
- Comparing prices across bookmakers.
- Reviewing results and tracking line movement.
- Finding arbitrage opportunities.
- Finding positive-EV betting opportunities.
- Researching markets for dashboards, alerts, bots, and other applications.
- Working with Betfair exchange prices and market data through the API.

The service covers sports including soccer, basketball, baseball, tennis, cricket, ice hockey, rugby, American football, MMA, table tennis, Aussie rules, CS2, and related supported leagues. Current availability should be discovered through the API because coverage changes over time.

## Limitations and notes

Using the MCP server depends on access to the Odds API and its available plans. Results and market coverage depend on the sports, leagues, bookmakers, and markets currently served by the API. A static sport or league list should not be treated as permanent; use the coverage endpoints for production discovery.

The repository also includes direct REST examples and SDKs, so MCP is not the only integration path. Teams that need raw HTTP requests, generated clients, or typed application integration may prefer those alternatives. Betfair live-market workflows use dedicated exchange endpoints and WebSocket subscription paths rather than the general odds queries.

_Full upstream README: https://allmcps.com/mcp/odds-api-net-mcp-server/readme_