MCP MCP Server

MCP server for odds-api

Local serverstdioPython

What is the MCP MCP server?

MCP server for odds-api. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

  1. Create _or edit the Claude Desktop configuration file located at: - On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - On Windows: %APPDATA%/Claude/claude_desktop_config.json
  • Uses environmental variables to limit the queries to some regions and a single sport

Its toolset

Everything the assistant can do here goes through one of these:

  • get_events — - Get in-play and forthcoming events (matches)
  • get_odds — - Get odds for all forthcoming events (matches) for selected betting markets
  • get_event_odds — - Get odds for a specific event (match) for selected betting markets
  • Setup — 2. Clone the Repository: bash git clone https://github.com/marcoeg/mcp-odds-api cd mcp-nvd

Configuration

You will need 3 environment variables: ODDS_API_KEY, ODDS_API_REGIONS, ODDS_API_SPORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — get_events, get_odds, get_event_odds and 1 more — is a fair guide to whether it matches your workflow. It is maintained by marcoeg; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
get_events- Get in-play and forthcoming events (matches).
get_odds- Get odds for all forthcoming events (matches) for selected betting markets.
get_event_odds- Get odds for a specific event (match) for selected betting markets.
Setup2. **Clone the Repository**: bash git clone https://github.com/marcoeg/mcp-odds-api cd mcp-nvd

How to install the MCP MCP server

{
  "mcpServers": {
    "mcp-bauplan": {
      "command": "/path/to/uvx",
      "args": ["mcp-odds-api"],
      "env": {
        "ODDS_API_KEY": "<your-api-odds-key>",
        "ODDS_API_REGIONS": "<region1>", "<region2>",
        "ODDS_API_SPORT": "<selected-sport-key>",
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ODDS_API_KEYCredential the server authenticates with.Yes
ODDS_API_REGIONSConfiguration value read at startup.Optional
ODDS_API_SPORTConfiguration value read at startup.Optional

Example prompts to try

  • Use MCP to get events.
  • Use MCP to get odds.
  • Use MCP to get event odds.

Frequently asked questions

You need Python 3.10 or higher, a valid OddsAPI key (request one at https://the-odds-api.com/account/), and the `uv` package manager installed.