get_player_props — DunkAPI MCP Tool Read-only

get_player_props (get player props) is one of 18 tools on the DunkAPI MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_player_props from your client

Claude Code DunkAPI get_player_props run in your project directory
Claude Desktop DunkAPI get_player_props ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor DunkAPI get_player_props ~/.cursor/mcp.json
VS Code DunkAPI get_player_props .vscode/mcp.json
Zed DunkAPI get_player_props ~/.config/zed/settings.json
Windsurf DunkAPI get_player_props ~/.codeium/windsurf/mcp_config.json
Cline DunkAPI get_player_props ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI DunkAPI get_player_props ~/.gemini/settings.json
Grok DunkAPI get_player_props .mcp.json (in your project root)
ChatGPT DunkAPI get_player_props Settings → Connectors → Advanced → Developer mode
Claude.ai DunkAPI get_player_props Settings → Connectors → Add custom connector
LangChain DunkAPI get_player_props pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http dunkapi https://mcp.dunkapi.com/mcp

Other tools on this server

list_teams
list_games
get_schedule
get_game
get_standings
get_injuries
search_players
get_player
get_player_games
get_leaders
get_team_stats
get_plays
get_shot_chart
get_odds
get_line_movement
get_ratings
get_prop_history

This list was read from the server itself, by connecting to it and calling tools/list on 11 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.

DunkAPI MCP server