World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Live tennis scores, players, rankings, odds and win-probability. ATP, WTA, Challenger, ITF, juniors.
Elige la app de IA que usas y copia la configuración.
Pasó 5/5 revisiones · Lo que preguntas pasa por el servidor del autor (mcp.livetennisapi.com) · ✓ Comandos revisados el 13 nov 2026
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude · unos 2 min
Sin clave y sin instalar nada · Configúralo una vez en claude.ai o en la app de escritorio y úsalo en el chat · las cuentas gratis pueden añadir 1 · en Team/Enterprise lo añade un Owner
CustomizeConnectors
Copia cada valor al campo con el mismo nombre en Claude y pulsa Continue
Livetennisapi MCPhttps://mcp.livetennisapi.com/mcpPulsa Continue en la pantalla de inicio de sesión que detectó Claude · en Authentication elige lo que indique el autor (Sign in now, Sign in when needed o No sign in) y pulsa Add
+ConnectorsLivetennisapi MCP
Usa Livetennisapi MCP y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando Livetennisapi MCP o muestra una herramienta de Livetennisapi MCP en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con ChatGPT según tu plan
MCP completo: ChatGPT Business, Enterprise o Edu en la web · Pro: conecta con permisos de lectura/obtención, así que las herramientas que cambian datos pueden no funcionar · Plus: no confirmado en la documentación; si ves una opción para añadir MCP propio en la página de plugins puedes probar · solo web
Plugins+Add custom MCP server
Pon un nombre, pega la dirección en Connection, marca el aviso de riesgo y pulsa Create as a plugin
Livetennisapi MCPhttps://mcp.livetennisapi.com/mcpAbre un chat nuevo y elige Livetennisapi MCP en tus plugins antes de escribir
Usa Livetennisapi MCP y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si ChatGPT dice que está usando Livetennisapi MCP o muestra una herramienta de Livetennisapi MCP en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de OpenAI el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Claude Code · unos 2 min
Sin clave y sin instalar nada
Mac: pulsa Command+Espacio y escribe Terminal · Windows: abre PowerShell
claude mcp add --transport http --scope user livetennisapi https://mcp.livetennisapi.com/mcpDeberías ver Livetennisapi MCP en la lista como conectado
Usa Livetennisapi MCP y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude Code dice que está usando Livetennisapi MCP o muestra una herramienta de Livetennisapi MCP en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Cursor · unos 2 min
Sin clave y sin instalar nada
Usa Livetennisapi MCP y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Cursor dice que está usando Livetennisapi MCP o muestra una herramienta de Livetennisapi MCP en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Cursor el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con VS Code · unos 2 min
Sin clave y sin instalar nada
Usa Livetennisapi MCP y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si VS Code dice que está usando Livetennisapi MCP o muestra una herramienta de Livetennisapi MCP en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de VS Code el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
Dirección para apps que se conectan por la web
https://mcp.livetennisapi.com/mcpLa configuración JSON está en “Para desarrolladores”, abajo
Claude Code
claude mcp add --transport http --scope user livetennisapi https://mcp.livetennisapi.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"livetennisapi": {
"url": "https://mcp.livetennisapi.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"livetennisapi": {
"type": "http",
"url": "https://mcp.livetennisapi.com/mcp"
}
}
}Claude Code
claude mcp add --scope user livetennisapi --env LIVETENNISAPI_KEY=your-value -- npx -y livetennisapi-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"livetennisapi": {
"command": "npx",
"args": [
"-y",
"livetennisapi-mcp"
],
"env": {
"LIVETENNISAPI_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"livetennisapi": {
"command": "npx",
"args": [
"-y",
"livetennisapi-mcp"
],
"env": {
"LIVETENNISAPI_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"livetennisapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"livetennisapi-mcp"
],
"env": {
"LIVETENNISAPI_KEY": "your-value"
}
}
}
}LIVETENNISAPI_KEY secreto obligatorio envDescripciones traducidas automáticamente; los nombres de variables quedan como en el original. Si dudas, mira el original.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
npm: livetennisapi-mcpSegún cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se conectan por internet en
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Nombres y descripciones de las herramientas tal como los informó el servidor el 13 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
get_live_matchesList 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).
get_upcoming_matchesList 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).
get_matchFull 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).
get_match_scoreCurrent 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).
search_playersSearch 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).
get_playerOne player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).
get_fixturesUpcoming 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).
search_tournamentsSearch 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).
get_tournamentOne 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).
get_recent_resultsRecently completed tennis matches with final scores and winners. Filterable by tour, player, nationality and play date. Requires the BASIC plan or any History plan.
search_archive_matchesSearch 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 Wimbl
get_archive_matchOne 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.
search_archive_playersThe 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
get_archive_careerOne 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
get_h2hThe 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
get_match_eventsTimeline of events for a match: breaks, games won, sets won, momentum runs. Requires the PRO plan.
get_match_oddsMatch-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.
get_rankingsThe 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 202
player_statsOne 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, come
get_match_analysisModel 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.
get_player_rankingsPoint-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:
get_match_statisticsIn-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 fa
get_charting_playerCareer 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 I
get_charting_matchEvery 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.
check_api_statusCheck 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.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 14 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub livetennisapi, dueña del repo
Último cambio de código: ayer
Usa MIT
Respondió en 770 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 25 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 5 de 5 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: LIVETENNISAPI_KEY
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
El repo de GitHub cambió por última vez ayer, y la última versión (1.6.5) llegó al registro hace 17 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también sirve en apps que aceptan MCP remoto, como ChatGPT en la web (MCP completo en Business y superiores; Pro solo lectura).
En la misma categoría: World Monitor, Claude Flow, Windmill
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Run Windmill scripts and flows and manage jobs, schedules, resources and variables.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
MCP server for the [Live Tennis API](https://livetennisapi.com).
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.
Documentation · Get a free API key
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 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?"*
| 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 — the smallest payload | FREE |
search_players | Find players by name | FREE |
get_player | Profile, ranking, country, handedness | FREE |
get_fixtures | Forward schedule | FREE |
search_tournaments | Tournament catalogue — surface, location, category | FREE |
get_tournament | One tournament by its stable id | FREE |
get_recent_results | Completed matches and winners | BASIC |
search_archive_matches | Results archive (1968–2022) — historical results with ranks and seeds at the time | BASIC |
get_archive_match | One archive result, with serve stats where the era recorded them | BASIC |
search_archive_players | Archive bios — hand, DOB, career-high rank | BASIC |
get_archive_career | Career W-L, titles and serve aggregates over the archive | BASIC |
get_h2h | Cross-era head-to-head — archive + current, one record | BASIC |
get_match_events | Breaks, games, sets, momentum runs | PRO |
get_match_odds | Match-winner prices — bid / ask / mid | PRO |
get_rankings | Full published ranking table per system (ATP, WTA, ITF circuits), any week | PRO |
player_stats | One player's W/L by surface, level and season, set-based record, recent matches; serve/return sums on ULTRA | PRO |
get_player_rankings | Point-in-time ranking records for specific players, as of any date | ULTRA |
get_match_statistics | In-play statistics — aces, serve split, hold/break %, break points | ULTRA |
get_charting_player | Career profile from shot-level charting data | ULTRA |
get_charting_match | One charted match, every stat family, per-set split | ULTRA |
get_match_analysis | Model thesis, win probability, key factors | ULTRA |
check_api_status | Reachability + which plan your key is on | — |
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.
| FREE | BASIC | PRO | ULTRA | |
|---|---|---|---|---|
| Matches, scores, players, fixtures, tournaments | ✅ | ✅ | ✅ | ✅ |
| Completed-match listings (results)¹ | — | ✅ | ✅ | ✅ |
| Results archive (1968–2022) + head-to-head¹ | — | ✅ | ✅ | ✅ |
| Match events, odds + rankings listing | — | — | ✅ | ✅ |
| Model analysis, as-of rankings, match statistics + charting | — | — | — | ✅ |
| $0 — no card | $9.99/mo | $29.99/mo | $99.99/mo |
¹ Also unlocked by any History plan, which works on top of a free key.
| FREE | BASIC | PRO | ULTRA | |
|---|---|---|---|---|
| Requests per minute | 30 | 60 | 300 | 600 |
| Requests per day | 100 | 1,000 | 10,000 | 500,000 |
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:
https://mcp.livetennisapi.com/mcp
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:
https://mcp.livetennisapi.com/mcp?token=twjp_…
?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:
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?"}], )
The authorization_token is sent as a bearer token, which is exactly what this server already accepts — no separate credential to obtain.
One command:
codex mcp add livetennisapi \
--url https://mcp.livetennisapi.com/mcp \ --bearer-token-env-var LIVETENNISAPI_KEY
Or write it to ~/.codex/config.toml yourself — Codex shares that file across the CLI, the IDE extension and the desktop app:
[mcp_servers.livetennisapi]
url = "https://mcp.livetennisapi.com/mcp" bearer_token_env_var = "LIVETENNISAPI_KEY"
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:
codex plugin marketplace add livetennisapi/livetennisapi-codex-plugin
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.npm install
npm run build LIVETENNISAPI_KEY=twjp_… node dist/index.js # speaks MCP over stdio node dist/http.js # speaks MCP over HTTP, port 8081
npm test # protocol + parity with livetennisapi-ai + transport isolation + rate limiting + tool output npm run test:mutation # proves those tests fail when the code breaks
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:
| 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](https://www.npmjs.com/p