SockOdds

What the SockOdds MCP server does

The SockOdds MCP server exposes Australian sports odds through the Model Context Protocol. It connects to SockOdds API v1 and returns decimal prices from the bookmakers available under the account's plan. Results can cover head-to-head, line, and total markets, with the time SockOdds recorded each price.

The server separates event discovery from price lookup. list_leagues reports supported leagues and the keys used by other calls. find_event turns natural-language searches such as a team matchup or tournament name into matching events, including start times and v1 event IDs. This is useful because v1 event IDs are not interchangeable with IDs from the older 0.x integration.

How it works

An agent can first select a league, search for an event, and then request odds for that event. get_odds returns bookmaker-level prices. best_price selects the highest price for one side of a specified market and includes the relevant field, while excluding prices from other lines.

fair_odds removes bookmaker margin using the prices available at the same line. For each bookmaker that quotes every outcome, the tool converts decimal odds to implied probabilities, normalizes them so they total 100%, and converts the results back into prices. It then averages the normalized probabilities across eligible bookmakers. The tool supports two-way and three-way markets and can also perform the calculation without making an API request.

The server caches responses for 60 seconds and does not retry failed requests. After a rate-limit response, it waits for the API's Retry-After period before accepting more calls. Requests report their object usage, which matters on SockOdds plans with monthly object limits.

Setup and configuration

The SockOdds MCP server requires Node.js 20 or later. Install it from npm by configuring an MCP client to run npx -y sockodds-mcp. Claude Code and Claude Desktop have documented configurations; other clients can use the same local stdio command when they support MCP servers.

Set SOCKODDS_API_KEY to authenticate with SockOdds. The key is sent as a Bearer authorization header rather than in the URL. For testing without an account, set SOCKODDS_DEMO=1; demo responses contain invented sample data, and the demo setting is ignored when an API key is present.

SOCKODDS_TIMEZONE controls displayed event start times and defaults to Australia/Sydney; UTC is also shown. SOCKODDS_BASE_URL defaults to the SockOdds v1 endpoint and normally should remain unset. An installation built from source can instead run the compiled Node entry point after npm install and npm run build.

Tools and capabilities

• list_leagues: Lists available leagues and their identifiers.
• find_event: Searches for events and returns start times and event IDs.
• get_odds: Retrieves bookmaker prices for head-to-head, line, and total markets.
• best_price: Finds the best price for one market side and line.
• fair_odds: Calculates margin-adjusted prices for two- or three-way markets, either from API data or supplied values.

The free Developer plan described in the source material provides six leagues, three bookmakers, 2,500 objects per UTC month, and ten requests per minute. Responses can omit bookmakers outside the account's plan.

Limitations and notes

The SockOdds MCP server does not provide a line-movement tool. Although the underlying API has recorded history, that endpoint requires the Pro plan and is unavailable to free-key users. Fair odds are estimates derived from bookmaker prices, not predictions, and prices can change after retrieval. Users should verify current prices with the bookmaker and follow applicable gambling requirements.

The server targets SockOdds API v1. Older 0.x event IDs and v2 configuration are not translated for v1. A client should restart after updating the npm package so it loads the current version, and searches should be repeated when moving from the older release.