prizepicksapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIZEPICKS_API_KEY | No | Enables the keyed tools. Optional; with no key the server lists five keyless tools. Free key, 100 credits a month, no card. | none |
| PRIZEPICKS_API_BASE_URL | No | Override for testing. | https://prizepicksapi.com |
| PRIZEPICKS_MCP_MAX_CHARS | No | Truncates very large tool results. | 60000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
PrizePicks player-prop data from prizepicksapi.com, an independent service not affiliated with PrizePicks. Keyless tools return demo rows and the official payout table; set PRIZEPICKS_API_KEY for the live board, line history, change feed, graded results and sportsbook comparison. Pass user_request on data tools.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| demo_projectionsA | Fictional sample PrizePicks projections with the exact live schema (is_demo: true). Use to learn the fields before calling live data. No key. |
| demo_line_historyB | Fictional line history for a demo projection id such as demo_nba_001. No key. |
| demo_changesC | Fictional change-feed events (offer.changed etc.) in the live schema. No key. |
| payout_tableA | Official PrizePicks standard entry payout multipliers (power and flex) with derived break-even probabilities. Real reference data, no key. Goblin, demon and adjusted-odds lines pay differently and are not estimated. |
| credit_costA | Quote how many credits a REST request path costs before running it, plus the plan list. No key. |
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 5 tools
Each tool targets a clearly distinct resource: demo projections, demo line history, demo change events, payout reference data, and credit-cost quoting. There is little chance of confusing one tool for another.
All names use readable snake_case and descriptive nouns, with a consistent demo_ prefix for the three demo endpoints. The set is not verb_noun based, but the convention remains predictable enough for an agent.
Five tools is well-scoped for a small demo/reference API surface, and each tool appears to serve a distinct purpose. There is no obvious bloat or missing count issue.
The surface is mostly demo/reference-only despite descriptions referencing live data, and there is no tool to actually run live projection, line history, or change-feed requests. credit_cost also quotes REST request costs without an accompanying request-execution tool, creating a notable dead end.