get_queued_solve — PokerData MCP Tool Read-only
get_queued_solve
(get queued solve) 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 get_queued_solve from your client
- Claude Code PokerData get_queued_solve run in your project directory
- Claude Desktop PokerData get_queued_solve ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PokerData get_queued_solve ~/.cursor/mcp.json
- VS Code PokerData get_queued_solve .vscode/mcp.json
- Zed PokerData get_queued_solve ~/.config/zed/settings.json
- Windsurf PokerData get_queued_solve ~/.codeium/windsurf/mcp_config.json
- Cline PokerData get_queued_solve ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PokerData get_queued_solve ~/.gemini/settings.json
- Grok PokerData get_queued_solve .mcp.json (in your project root)
- ChatGPT PokerData get_queued_solve Settings → Connectors → Advanced → Developer mode
- Claude.ai PokerData get_queued_solve Settings → Connectors → Add custom connector
- LangChain PokerData get_queued_solve 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
- list_my_opponents
- get_opponent_notes
- get_opponent_limp_range
- enqueue_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.