Skip to main content
ClaudeWave

MCP server for the Live Tennis API — give Claude, Cursor and other LLM agents real-time tennis scores, odds and model win-probability

MCP ServersOfficial Registry249 stars11 forksJavaScriptMITUpdated today
Install in Claude Code / Claude Desktop
Method: NPX · livetennisapi-mcp
Claude Code CLI
claude mcp add livetennisapi-mcp -- npx -y livetennisapi-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "livetennisapi-mcp": {
      "command": "npx",
      "args": ["-y", "livetennisapi-mcp"],
      "env": {
        "LIVETENNISAPI_KEY": "<livetennisapi_key>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Detected environment variables
LIVETENNISAPI_KEY
Use cases

MCP Servers overview

<div align="center">

<img src="https://raw.githubusercontent.com/livetennisapi/.github/main/profile/banner.jpg" alt="Live Tennis API" width="640">

# livetennisapi-mcp

**MCP server for the [Live Tennis API](https://livetennisapi.com).**

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

[![npm](https://img.shields.io/npm/v/livetennisapi-mcp.svg)](https://www.npmjs.com/package/livetennisapi-mcp)
[![license](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)

[**Documentation**](https://docs.livetennisapi.com) · [**Get a free API key**](https://livetennisapi.com/subscribe/free)

</div>

---

## Setup

**Claude Code**

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

**Claude Desktop** — add to `claude_desktop_config.json`:

```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 **free** key (no card) at [livetennisapi.com](https://livetennisapi.com/subscribe/free), or a paid plan at [pricing](https://livetennisapi.com/#pricing).

## 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 | FREE |
| `get_upcoming_matches` | Matches starting soon | FREE |
| `get_match` | Full detail for one match | FREE |
| `get_match_score` | Current score only — fastest read | FREE |
| `search_players` | Find players by name | FREE |
| `get_player` | Profile, ranking, country, handedness | FREE |
| `get_fixtures` | Forward schedule | FREE |
| `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

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

Built on the official [`livetennisapi`](https://www.npmjs.com/package/livetennisapi)
client.

## Related

Everything in the Live Tennis API developer surface:

| | Install | Source | Package |
|---|---|---|---|
| Python client | `pip install livetennisapi` | [repo](https://github.com/livetennisapi/livetennisapi-python) | [package](https://pypi.org/project/livetennisapi/) |
| JavaScript / TypeScript client | `npm install livetennisapi` | [repo](https://github.com/livetennisapi/livetennisapi-js) | [package](https://www.npmjs.com/package/livetennisapi) |
| MCP server for LLM agents **(this repo)** | `npx livetennisapi-mcp` | — | [package](https://www.npmjs.com/package/livetennisapi-mcp) |

- **API reference** — <https://docs.livetennisapi.com> ([plain-HTML version](https://docs.livetennisapi.com/reference.html), no JavaScript required)
- **OpenAPI 3.1 specification** — [livetennisapi/openapi](https://github.com/livetennisapi/openapi)
- **Website and plans** — <https://livetennisapi.com>

## Licence

MIT — see [LICENSE](LICENSE). Use of the API service is governed by the
[Terms of Service](https://livetennisapi.com/terms).
aiclaudelive-scoresllmmcpmcp-servermodel-context-protocolsports-apisports-datatennistennis-apitypescript

What people ask about livetennisapi-mcp

What is livetennisapi/livetennisapi-mcp?

+

livetennisapi/livetennisapi-mcp is mcp servers for the Claude AI ecosystem. MCP server for the Live Tennis API — give Claude, Cursor and other LLM agents real-time tennis scores, odds and model win-probability It has 249 GitHub stars and was last updated today.

How do I install livetennisapi-mcp?

+

You can install livetennisapi-mcp by cloning the repository (https://github.com/livetennisapi/livetennisapi-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is livetennisapi/livetennisapi-mcp safe to use?

+

livetennisapi/livetennisapi-mcp has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.

Who maintains livetennisapi/livetennisapi-mcp?

+

livetennisapi/livetennisapi-mcp is maintained by livetennisapi. The last recorded GitHub activity is from today, with 6 open issues.

Are there alternatives to livetennisapi-mcp?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy livetennisapi-mcp to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: livetennisapi/livetennisapi-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/livetennisapi-livetennisapi-mcp)](https://claudewave.com/repo/livetennisapi-livetennisapi-mcp)
<a href="https://claudewave.com/repo/livetennisapi-livetennisapi-mcp"><img src="https://claudewave.com/api/badge/livetennisapi-livetennisapi-mcp" alt="Featured on ClaudeWave: livetennisapi/livetennisapi-mcp" width="320" height="64" /></a>

More MCP Servers

livetennisapi-mcp alternatives