Skip to main content
Glama
prizepicksapi-mcp

prizepicksapi-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PRIZEPICKS_API_KEYNoEnables 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_URLNoOverride for testing.https://prizepicksapi.com
PRIZEPICKS_MCP_MAX_CHARSNoTruncates 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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 5 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness2/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues