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