Log inSubmit server
Odds Api logo

Odds Api

Fetches sportsbook odds, events, scores, sports lists, and quota data from The Odds API through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Odds Api

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "odds-api-2": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-odds-api"
      ],
      "env": {
        "PLATFORM_ODDS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-odds-api

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 12d ago.

Overview

Odds Api MCP server exposes The Odds API to AI agents through tools for sports discovery, sportsbook odds, event data, scores, and quota checks. It can connect through the Pipeworx gateway or run locally as a stdio package with npx. Use it when an agent needs current or event-specific betting data across supported sports and leagues. Gateway access supports a platform key or a caller-provided API key, while the standalone package uses the supplied key mechanism.

Use cases

  • List available sports and leagues before querying odds
  • Compare current sportsbook odds across bookmakers
  • Retrieve player props and other event-specific markets
  • Check live scores and upcoming events
  • Monitor remaining API credits

Key features

  • Sports and league discovery
  • Current and event-specific odds
  • Live and recent scores
  • Upcoming and live event listings
  • API quota visibility
  • Gateway or local stdio deployment

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-odds-api (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads442Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Odds Api works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Odds Api

Odds Api is an MCP server that connects AI agents to The Odds API and exposes tools for listing sports, retrieving current or event-specific odds, checking scores and events, and viewing API quota. It can run through the Pipeworx gateway or locally over stdio.

Run `npx -y @pipeworx/mcp-odds-api` or configure that command in an MCP client. This starts the standalone stdio server without a Pipeworx account. For hosted access, add `https://gateway.pipeworx.io/odds-api/mcp` to the client's MCP configuration.

Yes, Odds Api works with Cursor through the hosted MCP endpoint. Add `https://gateway.pipeworx.io/odds-api/mcp` to Cursor's MCP configuration, then provide the platform key or a caller-supplied `_apiKey` as required.

Call `odds_api_quota()` to see credits used and remaining for the key serving the request. This tool is free, does not consume upstream credit, and reports an account-limited condition when the balance reaches zero.

Related MCP servers

All in Sports All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOdds Api AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/odds-api-2?style=directory)](https://allmcps.com/mcp/odds-api-2)
HTML Embed
<a href="https://allmcps.com/mcp/odds-api-2"><img src="https://allmcps.com/api/badge/odds-api-2?style=directory" alt="Odds Api on AllMCPs" /></a>