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.
Documentation · Get an API key
Setup
Claude Code
claude mcp add livetennis -e LIVETENNISAPI_KEY=twjp_… -- npx -y livetennisapi-mcpClaude 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 |
| Matches in progress, with live scores | BASIC |
| Matches starting soon | BASIC |
| Full detail for one match | BASIC |
| Current score only — fastest read | BASIC |
| Find players by name | BASIC |
| Profile, ranking, country, handedness | BASIC |
| Forward schedule | BASIC |
| Completed matches and winners | BASIC |
| Breaks, games, sets, momentum runs | PRO |
| Match-winner prices — bid / ask / mid | PRO |
| Model thesis, win probability, key factors | ULTRA |
| 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 stdioBuilt on the official livetennisapi
client.
Related
Everything in the Live Tennis API developer surface:
Install | Source | Package | |
Python client |
| ||
JavaScript / TypeScript client |
| ||
MCP server for LLM agents (this repo) |
| — |
API reference — https://docs.livetennisapi.com (plain-HTML version, no JavaScript required)
OpenAPI 3.1 specification — livetennisapi/openapi
Website and plans — https://livetennisapi.com
Licence
MIT — see LICENSE. Use of the API service is governed by the Terms of Service.
This server cannot be installed
Maintenance
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
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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