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