get_archive_match — livetennisapi mcp MCP Tool Read-only
get_archive_match
(get archive match) 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_archive_match from your client
- Claude Code livetennisapi mcp get_archive_match run in your project directory
- Claude Desktop livetennisapi mcp get_archive_match ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor livetennisapi mcp get_archive_match ~/.cursor/mcp.json
- VS Code livetennisapi mcp get_archive_match .vscode/mcp.json
- Zed livetennisapi mcp get_archive_match ~/.config/zed/settings.json
- Windsurf livetennisapi mcp get_archive_match ~/.codeium/windsurf/mcp_config.json
- Cline livetennisapi mcp get_archive_match ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI livetennisapi mcp get_archive_match ~/.gemini/settings.json
- Grok livetennisapi mcp get_archive_match .mcp.json (in your project root)
- ChatGPT livetennisapi mcp get_archive_match Settings → Connectors → Advanced → Developer mode
- Claude.ai livetennisapi mcp get_archive_match Settings → Connectors → Add custom connector
- LangChain livetennisapi mcp get_archive_match pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http livetennisapi-mcp https://mcp.livetennisapi.com/mcp
Other 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
- search_archive_players
- get_archive_career
- get_h2h
- get_match_events
- 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.