search — DraftKings API MCP Tool Read-only
search
(search) is one of 31 tools on the
DraftKings API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search from your client
- Claude Code DraftKings API search run in your project directory
- Claude Desktop DraftKings API search ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DraftKings API search ~/.cursor/mcp.json
- VS Code DraftKings API search .vscode/mcp.json
- Zed DraftKings API search ~/.config/zed/settings.json
- Windsurf DraftKings API search ~/.codeium/windsurf/mcp_config.json
- Cline DraftKings API search ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DraftKings API search ~/.gemini/settings.json
- Grok DraftKings API search .mcp.json (in your project root)
- ChatGPT DraftKings API search Settings → Connectors → Advanced → Developer mode
- Claude.ai DraftKings API search Settings → Connectors → Add custom connector
- LangChain DraftKings API search pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http server https://draftkingsapi.com/api/mcp
Other tools on this server
- fetch
- start_signup
- finish_signup
- send_feedback
- complete_setup
- get_live_board
- get_demo_sample
- get_api_directory
- get_live_connection
- get_coverage
- get_pick6_projections
- get_pick6_history
- get_pick6_line_history
- get_pick6_stream_snapshot
- get_sportsbook_scopes
- get_sportsbook_snapshot
- get_sportsbook_events
- get_sportsbook_odds
- get_sportsbook_history
- get_dfs_sports
- get_dfs_contests
- get_dfs_slates
- get_dfs_players
- get_context_games
- get_context_player_stats
- get_context_team_stats
- get_stats_games
- get_stats_player_games
- get_stats_team_games
- get_setup_fields
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.