Log inSubmit server
Livetennisapi MCP logo

Livetennisapi MCP

by livetennisapi

Read-only MCP tools for live tennis, schedules, players, results, rankings, odds, statistics, and model analysis.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Livetennisapi MCP

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": {
    "livetennisapi-livetennisapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livetennisapi-mcp"
      ],
      "env": {
        "LIVETENNISAPI_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.

Automated check passed— started and listed 24 tools correctly (26d ago).

Overview

livetennisapi/livetennisapi-mcp MCP server connects MCP clients to the Live Tennis API through local stdio or a hosted Streamable HTTP endpoint. It exposes read-only tools for live and upcoming matches, player and tournament data, fixtures, results, rankings, odds, statistics, historical archives, and model analysis across ATP, WTA, Challenger, ITF, and junior tennis. Free-plan tools cover core live data, while historical results, odds, rankings, statistics, charting, and analysis require higher API plans. Reach for it when an agent needs current tennis data or structured historical tennis research rather than general web search.

Use cases

  • Monitor matches currently in progress
  • Find upcoming fixtures and match ids
  • Research historical results and head-to-head records
  • Compare rankings, odds, and model probabilities
  • Inspect live match events and statistics

Key features

  • Live scores across ATP, WTA, Challenger, ITF, and juniors
  • Player, tournament, fixture, and ranking data
  • 1968–2022 results archive and cross-era head-to-heads
  • Match events, odds, statistics, and model analysis
  • Match Charting Project player and match data
  • Plan-aware API status and access explanations

Tools24

What Livetennisapi MCP lets your agent do. Expand a tool for its parameters.

Verified live~4.4k tokens of context

Security & health

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

ActiveLast checked 1d ago

Recent health check succeeded.

15/55 checks healthy over the last 76d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · livetennisapi-mcp (npm)

Adoption & maintenance

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

GitHub stars147Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed24Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Livetennisapi MCP works

What livetennisapi/livetennisapi-mcp does

livetennisapi/livetennisapi-mcp MCP server exposes the Live Tennis API to AI clients as read-only tools. The data covers ATP, WTA, Challenger, ITF, and junior competitions. Core tools list matches in progress, matches starting soon, current scores, player profiles, tournament records, and the forward fixture schedule.

The server also supports completed results and historical research. BASIC or History access provides recent results, a 1968–2022 results archive, archive player records, career summaries, and cross-era head-to-head data. PRO access adds match events, match-winner prices, and full published ranking tables. ULTRA access adds model win probabilities, match statistics, point-in-time player rankings, and Match Charting Project data for players and individual matches.

How it works

A client calls named MCP tools, and the server sends requests to the Live Tennis API using the configured key. Tools that need an identifier can use values returned by earlier searches: for example, search_players returns a player id for get_player, while tournament and match objects expose ids used by detail tools.

Archive player ids are separate from current roster ids. The archive covers completed results from 1968 through 2022, while the service’s own recent results begin in 2023. get_h2h combines both periods. Historical and point-in-time queries preserve the requested date boundary rather than substituting a newer record.

Plan restrictions are returned as plain-English results rather than only a bare authorization error. check_api_status reports reachability and the plan associated with the configured key. Responses can also expose rate-limit information; the documented quotas vary by plan, from 100 requests per day on FREE to 500,000 on ULTRA.

Setup and configuration

Run the local server with Node.js and npx:

Terminal
npx -y livetennisapi-mcp

Set the LIVETENNISAPI_KEY environment variable to an API key before starting it. A free key is available without a payment card. Claude Code can register the command with claude mcp add; Claude Desktop, Cursor, Zed, and other MCP clients use the same command and environment variable configuration.

The hosted Streamable HTTP endpoint is https://mcp.livetennisapi.com/mcp. It accepts a bearer token, an X-API-Key header, or a token query parameter. Headers are preferable when the client supports them because query parameters place the key in the connector configuration. The hosted endpoint has its own per-caller transport limit, separate from the upstream API quota.

Tools and capabilities

  • Query live, upcoming, recent, and archived matches.
  • Retrieve scores, match details, events, odds, statistics, and model analysis.
  • Search current players, archive players, tournaments, and charted matches.
  • Retrieve player profiles, rankings, career archive summaries, and head-to-head records.
  • Inspect tournament metadata, fixtures, charting profiles, and historical serve data.
  • Check API reachability and the configured subscription plan.

Limitations and notes

The livetennisapi/livetennisapi-mcp MCP server does not provide every capability on every plan. FREE covers the core match, player, fixture, and tournament tools; BASIC or a History plan is needed for completed results and archive queries; PRO is needed for events, odds, and ranking tables; ULTRA is needed for analysis, detailed statistics, point-in-time player rankings, and charting.

Archive serve statistics are unavailable for many records before 1991 and are omitted rather than generated. Match Charting Project coverage is curated and concentrated on major events, not a complete tennis schedule. Measured match-statistic fields vary by tour and absent values are not filled with zeroes. FREE access is limited to 100 daily requests, so frequent polling requires attention to the selected plan and quota.

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 Livetennisapi MCP

livetennisapi/livetennisapi-mcp is an MCP server that connects AI clients to the Live Tennis API and exposes read-only tools for live matches, scores, players, fixtures, tournaments, results, rankings, odds, match analysis, statistics, charting, and head-to-head data. Tool availability depends on the API key’s plan.

Run `npx -y livetennisapi-mcp` and provide the `LIVETENNISAPI_KEY` environment variable. No separate package installation is required because npx fetches the server when it starts.

Yes, it works with Cursor through the standard command and environment variable configuration. Add `npx -y livetennisapi-mcp` as the MCP server command and set `LIVETENNISAPI_KEY` to an API key.

You need the BASIC plan or any History plan for recent completed results, the 1968–2022 archive, archive player and career tools, and head-to-head records. Core live match and player tools work on the FREE plan.

Call `check_api_status` to check API reachability and identify the plan associated with the configured key. Tier-limited tools also return a plain-English explanation when the current plan does not include the requested data.

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