# Odds Api [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/pipeworx-io/mcp-odds-api  
**GitHub Stars:** 1  
**npm Downloads (last month):** 442  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/odds-api-2

## Description
The Odds API MCP — sportsbook odds across 70+ books, 30+ leagues

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

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

**Requires environment variables:** `PLATFORM_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 the Odds Api MCP server does

The Odds Api MCP server connects MCP-compatible clients and agents to The Odds API, which provides sportsbook data across more than 70 books and over 30 sports leagues. Supported coverage named by the project includes NFL, NBA, MLB, NHL, soccer, MMA, golf, tennis, esports, and cricket.

The server exposes tools for discovering available sports, retrieving current odds, checking odds for one event, listing upcoming or live events, reading live and recent final scores, and checking the serving API key's quota. The gateway endpoint also exposes shared Pipeworx meta-tools, while the standalone package exposes only the odds-related tools.

## How it works

A client can connect to the hosted MCP endpoint at `https://gateway.pipeworx.io/odds-api/mcp`. The same gateway also offers a full endpoint at `https://gateway.pipeworx.io/mcp`; the pack endpoint lists the odds tools directly, while the full endpoint lists tools from the broader catalog. The gateway can route questions through `ask_pipeworx`, including questions that fall outside the odds pack.

For local use, install or run `@pipeworx/mcp-odds-api` with npx. The package communicates over stdin and stdout using MCP and responds to `initialize`, `tools/list`, and `tools/call`. It does not add the shared gateway meta-tools when run locally.

## Setup and configuration

For gateway access, add the hosted URL to an MCP client such as Claude Desktop, Cursor, or Windsurf. Authentication can use the gateway's `PLATFORM_ODDS_API_KEY`, or a caller can provide an Odds API key with the `_apiKey` parameter after registering with The Odds API.

The standalone configuration uses `npx -y @pipeworx/mcp-odds-api` as the command and does not require a Pipeworx account. The source API is `https://api.the-odds-api.com/v4/` and receives the key through an `apiKey` query parameter.

## Tools and capabilities

The Odds Api MCP server provides these pack-specific tools:

- `list_sports(all?)` lists available sports and leagues.
- `get_odds(...)` retrieves current odds, with options for regions, markets, odds and date formats, bookmakers, and events.
- `get_event_odds(...)` retrieves odds for a specific event and can expose additional markets such as player props.
- `get_scores(...)` returns live and recent final scores.
- `get_events(...)` lists upcoming and live events.
- `odds_api_quota()` reports credits used and remaining for the key serving the request.

## Limitations and notes

The free tier provides 500 requests per month. Each odds-payload market counts as one request. `list_sports`, `get_events`, and `odds_api_quota` are described as free and do not consume upstream credits. `get_odds`, `get_event_odds`, and `get_scores` are metered.

When credits are exhausted, metered tools return `upstream_throttled` and suggest using a personal key. The upstream service may return HTTP 401 for both an exhausted balance and an invalid key, so the quota response and its message are needed to distinguish those cases. Credits reset on the plan anniversary rather than necessarily on the first day of a month.

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