draftkingsapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAFTKINGS_API_KEY | No | API key used by the keyed tools. Optional; leave it unset to use only the keyless tools. | |
| DRAFTKINGS_API_BASE | No | Overrides the API origin (for testing). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_public_boardA | Delayed, capped DraftKings Pick6 board: player, stat, line, multipliers, start time, plus recent line moves. No key needed, no credits. |
| get_public_sportsbookA | DraftKings Sportsbook moneyline, spread and total prices per game. No key needed, no credits. |
| get_public_line_movesB | Recent Pick6 and sportsbook line moves with previous and current line. No key needed, no credits. |
| get_demo_sampleA | Frozen sample rows that show a dataset's response shape. Never present them as data. No key needed, no credits. |
| get_credit_costsA | Credits each endpoint costs, optionally for a path and row count. No key needed, no credits. |
| get_statusA | Measured collection status: jobs, workers and the freshness of each dataset. No key needed, no credits. |
| get_history_coverageA | When stored history starts for each league, with capture counts. No key needed, no credits. |
| get_coverageB | Live coverage of every dataset for your key. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_sportsbook_eventsB | DraftKings Sportsbook events and start times. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_oddsB | Current DraftKings Sportsbook prices by event and market, with age and stale flags. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_odds_historyC | Stored DraftKings Sportsbook price history for an event or offer. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_pick6_projectionsB | Current DraftKings Pick6 lines with multipliers, full board, every league. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_pick6_historyB | Every recorded Pick6 line, multiplier and availability change, oldest first. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_pick6_line_historyB | Recorded moves for one Pick6 prop (pickable_id from get_pick6_projections or get_public_board id). Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_dfs_slatesB | DraftKings DFS slates by sport. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_dfs_contestsB | DraftKings DFS contests with entry fee, prize pool and entries. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_dfs_playersB | DraftKings DFS players with salaries and positions for a slate. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_compareB | Pick6 lines next to DraftKings Sportsbook lines for the same player, stat and game, with the gap. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_compare_booksC | Lines across books with an optional fair price. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_evC | Prices with positive expected value against a fair line. Analysis, not advice. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_arbitrageC | Arbitrage and middle opportunities across books. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_stats_player_gamesB | Player game logs for a sport and season. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
| get_stats_gamesB | Game results for a sport and season. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools map to distinct resources, but several near-pairs exist: get_public_board vs get_pick6_projections (capped/keyless vs full keyed board), get_public_sportsbook vs get_odds, and get_compare vs get_compare_books. The three meta tools (get_coverage, get_history_coverage, get_status) and four history tools (get_odds_history, get_pick6_history, get_pick6_line_history, get_public_line_moves) also require careful reading to separate. Descriptions do provide enough signal to disambiguate, but selection errors are plausible.
All 23 tools use a uniform get_ prefix with snake_case noun phrases, giving a highly predictable surface. Minor deviations exist in word ordering and qualifiers (get_stats_player_games vs get_dfs_players, get_pick6_history vs get_pick6_line_history, the 'public_' keyless marker), but the pattern is still readable.
23 tools is on the heavy side and largely driven by the free/keyless vs API-key duplication of the same underlying data (public_board vs pick6_projections, public_sportsbook vs odds). The breadth across Pick6, sportsbook, DFS, stats and analysis partially justifies the count, but the surface feels bloated.
Coverage is broad: sportsbook events/odds/history, Pick6 projections and line history, DFS slates/contests/players, player and game stats, cross-book comparison, EV and arbitrage, plus meta tools for coverage, status and credit costs. Gaps are minor, e.g. no explicit markets/futures enumeration or contest-level result lookup, but core workflows have no dead ends.