get_match_events — livetennisapi mcp MCP Tool Read-only
get_match_events
(get match events) is one of 24 tools on the
livetennisapi mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_match_events from your client
- Claude Code livetennisapi mcp get_match_events run in your project directory
- Claude Desktop livetennisapi mcp get_match_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor livetennisapi mcp get_match_events ~/.cursor/mcp.json
- VS Code livetennisapi mcp get_match_events .vscode/mcp.json
- Zed livetennisapi mcp get_match_events ~/.config/zed/settings.json
- Windsurf livetennisapi mcp get_match_events ~/.codeium/windsurf/mcp_config.json
- Cline livetennisapi mcp get_match_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI livetennisapi mcp get_match_events ~/.gemini/settings.json
- Grok livetennisapi mcp get_match_events .mcp.json (in your project root)
- ChatGPT livetennisapi mcp get_match_events Settings → Connectors → Advanced → Developer mode
- Claude.ai livetennisapi mcp get_match_events Settings → Connectors → Add custom connector
- LangChain livetennisapi mcp get_match_events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http livetennisapi-mcp https://mcp.livetennisapi.com/mcpOther tools on this server
- get_live_matches
- get_upcoming_matches
- get_match
- get_match_score
- search_players
- get_player
- get_fixtures
- search_tournaments
- get_tournament
- get_recent_results
- search_archive_matches
- get_archive_match
- search_archive_players
- get_archive_career
- get_h2h
- get_match_odds
- get_rankings
- get_match_analysis
- get_player_rankings
- get_match_statistics
- get_charting_player
- get_charting_match
- check_api_status
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.