Log inSubmit server
Odds Api.net MCP Server logo

Odds Api.net MCP Server

Query sports and racing odds, compare bookmakers, track line movement, and research betting markets through MCP.

  • Verified ownerThe owner proved control of this listing (GitHub README, site badge or DNS record).
  • InstallableWe know how to install it, but have not yet seen it complete a handshake.
  • Health: ActiveRecent health check succeeded.Last checked 1d ago · Nov 12, 2026, 08:45 UTC
  • Sports
  • 39stars
  • No ratings User RatingsBe the first to rate and review this MCP server!
  • UpdatedNov 5, 2026
InstallRepositoryWebsite
Get support Full README Compare alternatives Embed widget

Install Odds Api.net MCP Server

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-net-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@odds-api/mcp"
      ],
      "env": {
        "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

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @odds-api/mcp

No response to initialize.

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 .

Overview

Sports and racing data flows through the odds-api.net MCP Server MCP server, which connects MCP-compatible coding agents to the Odds API. Its tools cover event and odds searches, bookmaker comparison, results, line movement, arbitrage, positive-EV analysis, and betting research. Requests use the API’s REST-backed data and require an Odds API key. Reach for it when an agent needs current market data for dashboards, alerts, bots, or analysis workflows.

Use cases

  • Search upcoming events and available odds
  • Compare bookmaker prices for a market
  • Track line movement across bookmakers
  • Find arbitrage and positive-EV opportunities
  • Build betting dashboards, alerts, or research tools

Key features

  • Sports and racing event and odds queries
  • Bookmaker comparison
  • Line movement tracking
  • Results and betting research
  • Arbitrage and positive-EV analysis
  • Betfair exchange market access

Security & health

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

ActiveLast checked

Recent health check succeeded.

8/9 checks healthy over the last 52d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 21h ago via OSV.dev · @odds-api/mcp (npm)

Adoption & maintenance

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

GitHub stars39Stargazers on the source repository.
npm downloads91Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Odds Api.net MCP Server works

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

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.net MCP Server

odds-api.net MCP Server is an MCP server that connects AI coding agents to the Odds API for sports and racing data. Its main tools support event and odds searches, bookmaker comparison, line-movement tracking, results, arbitrage, positive-EV analysis, and betting research using the API’s REST-backed data.

Set the `ODDS_API_KEY` environment variable with an API key from odds-api.net. The default API base URL is `https://api.odds-api.net/v1`; set `ODDS_API_BASE_URL` to override it. Use `ODDS_API_MOCK=1` for local mock-mode examples.

Yes, Cursor is named as a supported MCP-compatible coding agent for this project. The repository also identifies Claude, Windsurf, and Cline as supported agent clients.

Yes, bookmaker comparison is one of its supported betting-data workflows. Agents can use the service to compare available prices across bookmakers, alongside event searches, odds retrieval, line movement, arbitrage, and positive-EV analysis.

Use the API’s coverage discovery resources, including `GET /v1/coverage`, `GET /v1/sports`, and `GET /v1/leagues`. Coverage changes as leagues, bookmakers, and markets are added or retired, so production applications should discover current availability.

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.net MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/odds-api-net-mcp-server?style=directory)](https://allmcps.com/mcp/odds-api-net-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/odds-api-net-mcp-server"><img src="https://allmcps.com/api/badge/odds-api-net-mcp-server?style=directory" alt="Odds Api.net MCP Server on AllMCPs" /></a>