get_player_matches — AcesAPI MCP Tool Read-only
get_player_matches
(get player matches) is one of 13 tools on the
AcesAPI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_player_matches from your client
- Claude Code AcesAPI get_player_matches run in your project directory
- Claude Desktop AcesAPI get_player_matches ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AcesAPI get_player_matches ~/.cursor/mcp.json
- VS Code AcesAPI get_player_matches .vscode/mcp.json
- Zed AcesAPI get_player_matches ~/.config/zed/settings.json
- Windsurf AcesAPI get_player_matches ~/.codeium/windsurf/mcp_config.json
- Cline AcesAPI get_player_matches ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AcesAPI get_player_matches ~/.gemini/settings.json
- Grok AcesAPI get_player_matches .mcp.json (in your project root)
- ChatGPT AcesAPI get_player_matches Settings → Connectors → Advanced → Developer mode
- Claude.ai AcesAPI get_player_matches Settings → Connectors → Add custom connector
- LangChain AcesAPI get_player_matches pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http acesapi https://mcp.acesapi.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 October 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.