Skip to main content
Glama
livetennisapi

livetennisapi-mcp

livetennisapi-mcp

MCP server for the Live Tennis API.

Give Claude, Cursor, Zed or any MCP client live tennis scores, players, odds and model win-probability — for ATP, WTA, Challenger and ITF.

npm license

Documentation · Get an API key


Setup

Claude Code

claude mcp add livetennis -e LIVETENNISAPI_KEY=twjp_… -- npx -y livetennisapi-mcp

Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "livetennis": {
      "command": "npx",
      "args": ["-y", "livetennisapi-mcp"],
      "env": { "LIVETENNISAPI_KEY": "twjp_…" }
    }
  }
}

Cursor / Zed / others — same command, same env var. No install step; npx fetches it on demand.

Get a key at livetennisapi.com.

Related MCP server: Odds-API MCP Server

Try it

"What tennis matches are live right now?" "Who's winning the Alcaraz match, and what does the model give him?" "Show me Sinner's ranking and recent results." "What are the current odds on match 18953?"

Tools

Tool

Does

Plan

get_live_matches

Matches in progress, with live scores

BASIC

get_upcoming_matches

Matches starting soon

BASIC

get_match

Full detail for one match

BASIC

get_match_score

Current score only — fastest read

BASIC

search_players

Find players by name

BASIC

get_player

Profile, ranking, country, handedness

BASIC

get_fixtures

Forward schedule

BASIC

get_recent_results

Completed matches and winners

BASIC

get_match_events

Breaks, games, sets, momentum runs

PRO

get_match_odds

Match-winner prices — bid / ask / mid

PRO

get_match_analysis

Model thesis, win probability, key factors

ULTRA

check_api_status

Reachability + which plan your key is on

Tier awareness

The API gates endpoints by plan and returns a bare 403 {"error":"upgrade_required"}. Handed that, a model will usually invent a reason or retry pointlessly.

So every tool that can hit a tier wall returns a plain-English explanation — as a normal result, not an error — naming the tier required and where to upgrade. The assistant can then tell you something true and actionable:

This data requires the ULTRA plan, and the configured API key is on a lower tier. Nothing is wrong with the key — the endpoint is simply not included in the current plan. Upgrade at https://livetennisapi.com/#pricing

check_api_status probes upward to report which plan your key is actually on, so you can diagnose that without guessing.

Plans

BASIC

PRO

ULTRA

Matches, scores, players, fixtures, results

Match events + odds

Model analysis + win probability

Notes

  • Read-only. Every tool is a GET; nothing here can modify anything.

  • Your key stays local. It is read from the environment by the server process on your machine and sent only to api.livetennisapi.com.

  • Requires Node 18+.

Development

npm install
npm run build
LIVETENNISAPI_KEY=twjp_… node dist/index.js   # speaks MCP over stdio

Built on the official livetennisapi client.

Everything in the Live Tennis API developer surface:

Install

Source

Package

Python client

pip install livetennisapi

repo

package

JavaScript / TypeScript client

npm install livetennisapi

repo

package

MCP server for LLM agents (this repo)

npx livetennisapi-mcp

package

Licence

MIT — see LICENSE. Use of the API service is governed by the Terms of Service.

A
license - permissive license
-
quality - not tested
A
maintenance

Maintenance

Maintainers
Response time
0dRelease cycle
2Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/livetennisapi/livetennisapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server