get_player_context — flash props api MCP Tool Read-only
get_player_context
(get player context) is one of 12 tools on the
flash props api
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_player_context from your client
- Claude Code flash props api get_player_context run in your project directory
- Claude Desktop flash props api get_player_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor flash props api get_player_context ~/.cursor/mcp.json
- VS Code flash props api get_player_context .vscode/mcp.json
- Zed flash props api get_player_context ~/.config/zed/settings.json
- Windsurf flash props api get_player_context ~/.codeium/windsurf/mcp_config.json
- Cline flash props api get_player_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI flash props api get_player_context ~/.gemini/settings.json
- Grok flash props api get_player_context .mcp.json (in your project root)
- ChatGPT flash props api get_player_context Settings → Connectors → Advanced → Developer mode
- Claude.ai flash props api get_player_context Settings → Connectors → Add custom connector
- LangChain flash props api get_player_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http flash-props-api https://api.flashodds.live/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.