get_prop_probabilities — PuckAPI MCP Tool Read-only
get_prop_probabilities
(get prop probabilities) is one of 28 tools on the
PuckAPI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_prop_probabilities from your client
- Claude Code PuckAPI get_prop_probabilities run in your project directory
- Claude Desktop PuckAPI get_prop_probabilities ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PuckAPI get_prop_probabilities ~/.cursor/mcp.json
- VS Code PuckAPI get_prop_probabilities .vscode/mcp.json
- Zed PuckAPI get_prop_probabilities ~/.config/zed/settings.json
- Windsurf PuckAPI get_prop_probabilities ~/.codeium/windsurf/mcp_config.json
- Cline PuckAPI get_prop_probabilities ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PuckAPI get_prop_probabilities ~/.gemini/settings.json
- Grok PuckAPI get_prop_probabilities .mcp.json (in your project root)
- ChatGPT PuckAPI get_prop_probabilities Settings → Connectors → Advanced → Developer mode
- Claude.ai PuckAPI get_prop_probabilities Settings → Connectors → Add custom connector
- LangChain PuckAPI get_prop_probabilities pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http puckapi https://mcp.puckapi.com/mcp
Other tools on this server
- get_standings
- get_team_stats
- list_teams
- get_games
- get_schedule
- get_game_detail
- get_head_to_head
- search_players
- get_player_stats
- get_goalie_stats
- get_skater_season_stats
- get_player_game_log
- get_odds
- get_line_movement
- get_player_props
- get_prop_history
- get_prop_movement
- get_market_odds
- get_game_probabilities
- get_prop_backtest
- get_plays
- get_shot_map
- get_shifts
- get_situation_time
- get_predictions
- get_prop_projections
- get_alt_lines
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.