Livetennisapi MCP Server

Real-time tennis scores, players, odds and model win-probability for ATP, WTA, Challenger, ITF.

Remote serverstreamable-httpPython

What is the Livetennisapi MCP server?

Livetennisapi MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Real-time tennis scores, players, odds and model win-probability for ATP, WTA, Challenger, ITF.

What you get

Give Claude, Cursor, Zed or any MCP client live tennis scores, players and fixtures — for ATP, WTA, Challenger and ITF. Odds and model win-probability tools are included, and require the PRO and ULTRA plans.

What the assistant can call

Once Livetennisapi is connected, these are the calls the assistant has available:

  • get_live_matches — Matches in progress, with live scores
  • get_upcoming_matches — Matches starting soon
  • get_match — Full detail for one match
  • get_match_score — Current score only — fastest read
  • search_players — Find players by name
  • get_player — Profile, ranking, country, handedness
  • get_fixtures — Forward schedule
  • search_tournaments — Tournament catalogue — surface, location, category
  • get_tournament — One tournament by its stable id
  • get_recent_results — Completed matches and winners
  • search_archive_matches — Results archive (1968–2022) — historical results with ranks and seeds at the time
  • get_archive_match — One archive result, with serve stats where the era recorded them

Configuration and credentials

You will need one environment variable: LIVETENNISAPI_KEY. 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.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

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. Livetennisapi's toolset — get_live_matches, get_upcoming_matches, get_match and 11 more — is a fair guide to whether it matches your workflow. It is maintained by livetennisapi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Livetennisapi's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Livetennisapi.
  • 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 livetennisapi mcp server does with a few real requests.

Available tools

ToolWhat it does
get_live_matchesMatches in progress, with live scores
get_upcoming_matchesMatches starting soon
get_matchFull detail for one match
get_match_scoreCurrent score only — fastest read
search_playersFind players by name
get_playerProfile, ranking, country, handedness
get_fixturesForward schedule
search_tournamentsTournament catalogue — surface, location, category
get_tournamentOne tournament by its stable id
get_recent_resultsCompleted matches and winners
search_archive_matchesResults archive (1968–2022) — historical results with ranks and seeds at the time
get_archive_matchOne archive result, with serve stats where the era recorded them
search_archive_playersArchive bios — hand, DOB, career-high rank
get_archive_careerCareer W-L, titles and serve aggregates over the archive

How to install the Livetennisapi MCP server

{
  "mcpServers": {
    "livetennisapi": {
      "command": "npx",
      "args": ["-y", "livetennisapi-mcp"],
      "env": {
        "LIVETENNISAPI_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LIVETENNISAPI_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Livetennisapi to get live matches.
  • Use Livetennisapi to get upcoming matches.
  • Use Livetennisapi to get match.

Frequently asked questions

It connects Livetennisapi to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_live_matches, get_upcoming_matches, get_match, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Livetennisapi directly.