Betsapi vs Livetennisapi MCP
A side-by-side look at the Betsapi and Livetennisapi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Betsapi for sports work as a local process; choose Livetennisapi MCP for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Betsapi when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
betsapi_inplay, betsapi_upcoming, betsapi_event_odds.
Choose Livetennisapi MCP when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LIVETENNISAPI_KEY. - You want tools like
get_live_matches, get_upcoming_matches, get_match.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 55/100 · Good | 50/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | None listed | LIVETENNISAPI_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 152 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 3 | 24 |
| Full listing | View Betsapi | View Livetennisapi MCP |
Tools & capabilities
Betsapi tools 3
betsapi_inplayLive in-play sport matches happening right now, with running score and match clock. Pass a sport_id (${SPORT_IDS}). Example: betsapi_inplay({ sport_id: "1", _apiKey: "your-key" })betsapi_upcomingUpcoming (scheduled) sport events for a sport, optionally for a given day. Pass a sport_id (${SPORT_IDS}) and optionally day=YYYYMMDD. Example: betsapi_upcoming({ sport_id: "1", day: "20260704", _apiKey: "your-key" })betsapi_event_oddsBookmaker odds for a single event across markets (moneyline, spreads, totals). Odds are deeply nested by market, so the full structure is returned under `raw`. Get an event_id from betsapi_inplay or betsapi_upcoming first. Example: betsapi_event_odds({ event_id: "12345678", _apiKey: "your-key" })
Livetennisapi MCP tools 24
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 — the fastest, lowest-latency read. Use this 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 — the forward schedule, filterable by tour, player and date. Use this for "what is on this week". Works on the FREE plan (no card needed).search_tournamentsSearch the tournament catalogue — the stable id space that match objects carry as tournament_id. 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. Winner/loser-shaped records with final score, 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 our own results (get_recent_results) begin. Requires the BASIC plan or any History plan.get_archive_matchOne result from the results archive (1968–2022), with per-match serve statistics where the era recorded them — stats are null for most rows before 1991, honestly, never synthesised. Requires the BASIC plan or any History plan.- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Betsapi
{
"mcpServers": {
"betsapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-betsapi"
]
}
}
}
Livetennisapi MCP
{
"mcpServers": {
"livetennisapi-livetennisapi-mcp": {
"command": "npx",
"args": [
"-y",
"livetennisapi-mcp"
],
"env": {
"LIVETENNISAPI_KEY": "YOUR_LIVETENNISAPI_KEY_HERE"
}
}
}
}
Frequently asked questions
Betsapi is categorized under Sports and uses a local stdio subprocess. Livetennisapi MCP belongs to Sports and uses a local stdio subprocess. Pick Betsapi for sports work and Livetennisapi MCP for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Betsapi is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Livetennisapi MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add betsapi and livetennisapi-livetennisapi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Betsapi has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Livetennisapi MCP has 50/100 (Good) with 5 views, 0 installs and 152 GitHub stars.