get_live_matches
Live matches
List tennis matches currently in progress, with live scores. Covers ATP, WTA, Challenger, ITF and juniors. Use this for "what tennis is on right now". Works on the FREE plan (no card needed).
tourlimitplayercountry
io.github.livetennisapi由 GitHub 账号 livetennisapi 发布v1.6.5更新于 Oct 30, 2026
Live tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors.
Live Tennis API 的 MCP 服务器,让助手获取 ATP、WTA、Challenger、ITF 和青少年赛事的实时比分、球员、赛程、排名、赔率与模型胜率。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.livetennisapi%2Flivetennisapi-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"livetennisapi": {
"type": "http",
"url": "https://mcp.livetennisapi.com/mcp"
}
}
}MCP server for the Live Tennis API.
Give Claude, Cursor, Zed or any MCP client live tennis scores, players and fixtures — for ATP, WTA, Challenger, ITF and juniors. Odds, rankings, match statistics, charting and model win-probability tools are included, and require the PRO and ULTRA plans.
Claude Code
Claude Desktop — add to claude_desktop_config.json:
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, or a paid plan at pricing.
"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?" "What's the all-time head-to-head between Borg and McEnroe?" "List Navratilova's Grand Slam finals from the archive." "Who was ATP #1 the week Alcaraz first entered the top 10?" "How is Sabalenka serving in her live match — aces, hold rate, break points?"
The six BASIC history tools are also unlocked by any History plan, which works
on top of a free key. The results archive (1968–2022) — ATP and WTA, main
draws, qualifying and the ITF/futures tiers — ends exactly where the current
results begin (2023), so search_archive_matches answers "Borg's Wimbledon
finals" and get_recent_results answers "yesterday's scores"; get_h2h spans
both in one call.
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 in place at https://livetennisapi.com/subscribe/upgrade
check_api_status probes upward to report which plan your key is actually on,
so you can diagnose that without guessing.
¹ Also unlocked by any History plan, which works on top of a free key.
FREE is 100 requests/day, so poll no faster than every 15 minutes on a free
key; for an always-on dashboard, BASIC is the plan to recommend. Every response
carries X-RateLimit-Limit / -Remaining / -Reset headers, and the tools
relay the three distinct 429 shapes honestly — per-minute (retry shortly),
daily cap (the error names the exact reset instant), and the abuse block
(don't retry; fix the loop).
Most people should use the stdio server above — your key never leaves your machine. For clients that can only speak HTTP, there is also a hosted Streamable-HTTP endpoint:
Send your key as Authorization: Bearer twjp_…, X-API-Key: twjp_…, or
?token= if your client cannot set headers. Tools are listable without a key,
so directories can introspect the server; calling one needs a key.
It is multi-tenant and holds no key of its own: every request builds its own server bound to the key that request presented, and there is deliberately no fallback to the host's environment. The endpoint applies its own transport-level limit per caller — 60 req/min anonymous, 300 keyed. That limit only protects this host process. It is not your API quota, which the API enforces per key and tier (see the quota table above).
Self-hosting it: deploy/install-http.sh and deploy/TUNNEL.md.
As a connector. In Claude, add a custom connector and paste the endpoint with your key as a query parameter — no OAuth, nothing to install:
?token= exists for clients that cannot set request headers. The tradeoff, stated
plainly: a key in a URL is not written to our logs, but it is visible to the CDN
in front of the endpoint and is stored in the connector's configuration. Prefer
Authorization: Bearer twjp_… wherever your client lets you set a header.
From the Messages API. Claude can call the endpoint directly. Both halves are
required — the server and a matching toolset entry; sending mcp_servers alone
is rejected as a validation error:
The authorization_token is sent as a bearer token, which is exactly what this
server already accepts — no separate credential to obtain.
One command:
Or write it to ~/.codex/config.toml yourself — Codex shares that file across the
CLI, the IDE extension and the desktop app:
Use bearer_token_env_var, not bearer_token: it keeps the key in your
environment rather than committing it to a config file.
There is also a Codex plugin, on its own marketplace:
That registers the marketplace; install the plugin from Codex's plugin picker. Source: livetennisapi-codex-plugin.
The stdio route works too, unchanged: npx -y livetennisapi-mcp.
The Claude Code plugin (.claude-plugin/plugin.json) also ships the
polymarket-tennis Agent Skill under skills/polymarket-tennis/.
It teaches Claude the observe-only
polymarket-tennis Python
package (market discovery, market-to-match matching, joined price/live-score
view), the free-tier budget (30 req/min, 100 requests/day), and the verbatim
retirement/walkover settlement rules for Polymarket, Polymarket US and Kalshi.
Canonical copy lives in the polymarket-tennis repo; this one is mirrored for
plugin installs. No order execution, ever.
api.livetennisapi.com.test:mutation is worth understanding before changing src/http.ts. It
reintroduces each bug the tests claim to catch and asserts the suite goes red.
It is not ceremony: the first version of the rate-limit test passed while the
limiter was bucketing every caller together.
Built on the official livetennisapi
client.
Everything in the Live Tennis API developer surface:
Know developers who need tennis data? The affiliate program pays 51% recurring commission for the life of every referred subscription — 30-day cookie, and the people you refer get 10% off.
MIT — see LICENSE. Use of the API service is governed by the Terms of Service.
来源:README.md,提交 679733e
Live matches
List tennis matches currently in progress, with live scores. Covers ATP, WTA, Challenger, ITF and juniors. Use this for "what tennis is on right now". Works on the FREE plan (no card needed).
tourlimitplayercountryUpcoming matches
List tennis matches scheduled to start soon, with players, tournament and start time. Use this for "who plays next" or to find a match id before it starts. Works on the FREE plan (no card needed).
tofromtourlimitplayercountryMatch detail
Full detail for one match by id: players, score, surface, round and status. Includes market prices on PRO and model analysis on ULTRA. Works on the FREE plan (no card needed).
match_id必填Match score
Current score for one match. This is the fastest read, with the lowest latency. Use it when you only need the score and already know the match id. Works on the FREE plan (no card needed).
match_id必填Search players
Search tennis players by name. Returns id, country, ranking and tour. Use the returned id with get_player. Works on the FREE plan (no card needed).
limitquery必填Player profile
One player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).
player_id必填Fixture schedule
Upcoming scheduled tennis fixtures, earliest first. This is the forward schedule, filterable by tour. Use this for "what is on this week". Works on the FREE plan (no card needed).
tourlimitTournament catalogue
Search the tournament catalogue. Its ids are the tournament_id that match objects carry. Returns surface, indoor, host city/country and category where curated. Works on the FREE plan (no card needed).
tourlimitqueryTournament detail
One tournament by its stable id, the tournament_id carried on match objects. Name, tour, surface, indoor, plus host city/country and category where curated. Works on the FREE plan (no card needed).
tournament_id必填Recent results
Recently completed tennis matches with final scores and winners. Filterable by tour, player, nationality and play date. Requires the BASIC plan or any History plan.
tofromtourlimitplayercountryResults archive (1968–2022)
Search the results archive: completed-match RESULTS from 1968 through 2022. ATP and WTA, main draws, qualifying and the ITF/futures tiers. Each record has winner and loser, final score, and seeds and ranks AT THE TIME of the match. Use this for historical questions ("Borg's Wimbledon finals"). The archive ends 2022-12-31, where the current results (get_recent_results) begin. Requires the BASIC plan or any History plan.
tofromtourlevellimitroundplayer_nameArchive result detail
One result from the results archive (1968 to 2022), with per-match serve statistics where the era recorded them. Stats are null for most rows before 1991, never synthesised. Requires the BASIC plan or any History plan.
archive_match_id必填Archive player bios
The people of the results archive (1968 to 2022): hand, date of birth, country, height, and career-high rank with the week it was first reached. Their ids are corpus person ids (the winner/loser player_id on archive results), not roster ids. For current players use search_players. Requires the BASIC plan or any History plan.
tourlimitquery必填Archive career aggregates
One player's whole career over the results archive (1968 to 2022). W-L record in total and by surface/level/year, titles, and summed serve statistics. The corpus records serve stats from 1991 only, so matches_with_stats says how many matches the serve block covers. The name must resolve to one person. An ambiguous fragment returns the candidate list to choose from. Requires the BASIC plan or any History plan.
name必填Head-to-head
The all-time record between two players, across BOTH halves of the product. That is the results archive (1968 to 2022) plus the completed matches from 2023 onward. Names are the keys. An ambiguous fragment returns the candidate list to choose from, and nothing is guessed. Totals count only meetings with a known winner. Walkovers and retirements are part of the record, and each meeting carries its outcome. Requires the BASIC plan or any History plan.
player1必填player2必填Match timeline
Timeline of events for a match: breaks, games won, sets won, momentum runs. Requires the PRO plan.
limitmatch_id必填Match market prices
Match-winner market prices for a match: implied probability per player, with bid, ask and mid. Requires the PRO plan. Match rows carry has_market, so check it first. A match with no market mapped has no prices to return.
limitmatch_id必填Rankings listing
The FULL published ranking table in rank order for one system, from the newest week at or before as_of. Rows carry player_name as published and a null player_id for players outside our roster, so the table has no silent holes. ATP/WTA history runs deep. The ITF circuits begin 2026-07-29. For point-in-time records of SPECIFIC players use get_player_rankings. Requires the PRO plan.
as_oflimitsystem必填Player record and splits
One player's record over completed singles matches from 2023 onward, by default the last 365 days. It gives W/L overall, over the last 12 months and by surface, venue, level and season. It also gives tiebreaks, deciding sets, the record after winning or losing the first set, comebacks, withdrawals and the last N matches. Every count carries its sample size, and a percentage on an empty sample is null, never 0. On ULTRA it adds serve_return: measured serve and return statistics summed over the window. Singles only, so a doubles-team id is refused. For 1968 to 2022 use get_archive_career. Requires the PRO plan (serve_return requires ULTRA).
tofromlastlevelsurfaceplayer_id必填Model analysis
Model analysis for a match: predicted win probability, the model's thesis and the main factors behind it. Requires the ULTRA plan. Match rows carry has_analysis, so check it first. A match with no thesis or profile has nothing to return.
match_id必填Player rankings as of a date
Point-in-time ranking records for SPECIFIC players. Per system, the newest record in force ON OR BEFORE as_of, never one dated after it. Every other ranking field in this API is the CURRENT value joined at read time. This one is the historical answer. Systems are never collapsed: ATP/WTA and the ITF circuits carry rank+points, UTR a rating. ITF and UTR history begins 2026-07-29. Requires the ULTRA plan.
as_ofsystemplayer_ids必填Match statistics
In-play (or final) statistics for one match, in TWO families kept separate on purpose. DERIVED is rebuilt from the point-by-point record (holds/breaks, break points, service/return points). MEASURED is counted per match. It includes what no point record can yield: aces, double faults, the serve split, winners/unforced errors. Measured coverage varies by tour. Absent fields are omitted, never zero-filled. Requires the ULTRA plan.
match_id必填Charting: player career profile
Career profile from shot-level charting data, summed over the player's charted matches. Serve placement (deuce/ad x wide/body/T), return depth and outcomes, net play, and clutch break/game/set-point serving. Also winners and errors by wing, and rally-length tendencies. COVERAGE IS CURATED, not full-slate: 11,646 charted matches back to the 1960s, concentrated on the majors. An ambiguous name returns the candidates to choose from. Requires the ULTRA plan.
name必填genderCharting: one match, every stat family
Every charting stat family for ONE charted match, both players, with the per-set split (set 1, set 2, ..., Total) exactly as charted. Charting ids are their own id space (1960 to 2026). Most of these matches have no counterpart in the live tables. Requires the ULTRA plan.
charting_match_id必填API status and plan
Check whether the Live Tennis API is reachable and which plan the configured key is on. Use it to find out why other tools are refusing data. Works with no key.
无需输入参数。
已满足适用检查项的 100%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
claude mcp add livetennis -e LIVETENNISAPI_KEY=twjp_… -- npx -y livetennisapi-mcp{ "mcpServers": { "livetennis": { "command": "npx", "args": ["-y", "livetennisapi-mcp"], "env": { "LIVETENNISAPI_KEY": "twjp_…" } } }}https://mcp.livetennisapi.com/mcphttps://mcp.livetennisapi.com/mcp?token=twjp_…client.beta.messages.create( model="claude-opus-4-8", max_tokens=4096, betas=["mcp-client-2025-11-20"], mcp_servers=[{ "type": "url", "name": "livetennisapi", "url": "https://mcp.livetennisapi.com/mcp", "authorization_token": os.environ["LIVETENNISAPI_KEY"], }], tools=[{"type": "mcp_toolset", "mcp_server_name": "livetennisapi"}], messages=[{"role": "user", "content": "What tennis is live right now?"}],)codex mcp add livetennisapi \ --url https://mcp.livetennisapi.com/mcp \ --bearer-token-env-var LIVETENNISAPI_KEY[mcp_servers.livetennisapi]url = "https://mcp.livetennisapi.com/mcp"bearer_token_env_var = "LIVETENNISAPI_KEY"codex plugin marketplace add livetennisapi/livetennisapi-codex-pluginnpm installnpm run buildLIVETENNISAPI_KEY=twjp_… node dist/index.js # speaks MCP over stdionode dist/http.js # speaks MCP over HTTP, port 8081
npm test # protocol + parity with livetennisapi-ai + transport isolation + rate limiting + tool outputnpm run test:mutation # proves those tests fail when the code breaks