list_my_opponents — PokerData MCP Tool Read-only
list_my_opponents
(list my opponents) is one of 29 tools on the
PokerData
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_my_opponents from your client
- Claude Code PokerData list_my_opponents run in your project directory
- Claude Desktop PokerData list_my_opponents ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PokerData list_my_opponents ~/.cursor/mcp.json
- VS Code PokerData list_my_opponents .vscode/mcp.json
- Zed PokerData list_my_opponents ~/.config/zed/settings.json
- Windsurf PokerData list_my_opponents ~/.codeium/windsurf/mcp_config.json
- Cline PokerData list_my_opponents ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PokerData list_my_opponents ~/.gemini/settings.json
- Grok PokerData list_my_opponents .mcp.json (in your project root)
- ChatGPT PokerData list_my_opponents Settings → Connectors → Advanced → Developer mode
- Claude.ai PokerData list_my_opponents Settings → Connectors → Add custom connector
- LangChain PokerData list_my_opponents pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pokerdata https://pokerdata.io/api/mcp
Other tools on this server
- list_games
- get_range
- get_node
- get_config
- list_spots
- list_postflop_packs
- get_postflop_node
- explain_combo
- get_board_report
- compare_strategies
- list_datasets
- get_tree_docs
- get_range_metadata
- get_exploitability
- get_postflop_range
- find_hands
- get_hand_results
- get_session_summary
- list_my_sessions
- get_tournament_results
- get_opponent_notes
- get_opponent_limp_range
- enqueue_solve
- get_queued_solve
- list_queued_solves
- list_library_solutions
- get_upload_link
- upload_hand_history
This list was read from the server itself, by connecting to it and calling tools/list on 16 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.