get_player — GridIron Data MCP Tool Read-only
get_player
(get player) is one of 21 tools on the
GridIron Data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_player from your client
- Claude Code GridIron Data get_player run in your project directory
- Claude Desktop GridIron Data get_player ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GridIron Data get_player ~/.cursor/mcp.json
- VS Code GridIron Data get_player .vscode/mcp.json
- Zed GridIron Data get_player ~/.config/zed/settings.json
- Windsurf GridIron Data get_player ~/.codeium/windsurf/mcp_config.json
- Cline GridIron Data get_player ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GridIron Data get_player ~/.gemini/settings.json
- Grok GridIron Data get_player .mcp.json (in your project root)
- ChatGPT GridIron Data get_player Settings → Connectors → Advanced → Developer mode
- Claude.ai GridIron Data get_player Settings → Connectors → Add custom connector
- LangChain GridIron Data get_player pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gridiron-data https://api.gridirondata.com/mcpOther tools on this server
- list_players
- search_players
- get_projections
- get_player_by_espn_id
- get_prop_probability
- get_defense_vs_position
- get_player_stats
- get_deviations
- get_snap_share
- get_matchups
- get_player_news
- request_news_scrape
- get_latest_news
- get_ros_projections
- get_schedule
- get_byes
- get_injury_changes
- get_player_by_gsis_id
- get_depth_chart
- get_inactives
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.