sharpapi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHARPAPI_KEY | Yes | Your SharpAPI key. Get a free key at https://sharpapi.io |
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 |
|---|---|
| list_sportsA | List the sports SharpAPI covers, with live and upcoming event counts for each. Call this first to discover valid sport ids for the other tools. |
| list_sportsbooksA | List the sportsbooks SharpAPI normalizes, with their ids. Use the returned ids for the |
| list_eventsA | List events (games) with ids, start times and teams. Use this to find an event id before fetching odds for it. |
| get_oddsA | Get normalized odds across sportsbooks. Returns American and decimal prices plus implied probability, one row per book/market/selection, so prices are directly comparable between books. |
| get_best_oddsA | Get the best available price per selection across all covered books. This is the line shopping view: one row per selection rather than one per book. |
| get_arbitrageB | Find cross-book arbitrage opportunities: sets of prices whose combined implied probability is under 100%, so backing every outcome locks a margin. Requires a Hobby plan or above. |
| get_evB | Find positive expected value (+EV) bets: prices that beat the fair probability implied by the wider market. Each opportunity carries a fairProbability field, which is the de-vigged number. Requires a Pro plan or above. |
| get_middlesA | Find middle opportunities: two prices on opposite sides with a gap where both bets can win. Sorted by quality unless told otherwise. |
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 8 tools
The list_* tools are clearly distinct, and get_arbitrage, get_ev, and get_middles each target a unique betting opportunity type. However, get_odds and get_best_odds have similar names and both return odds, so an agent could initially confuse raw normalized odds with the line-shopping view.
Tool names follow a clean and predictable pattern: list_* for discovery endpoints and get_* for odds/opportunity lookups. Even the abbreviated get_ev fits the naming scheme, and all names use consistent snake_case formatting.
Eight tools is well-scoped for a sports betting odds API. The set covers discovery, odds retrieval, and specialized betting opportunity searches without unnecessary bloat or missing critical endpoints.
The toolkit covers the core workflow: discover sports and sportsbooks, find events, fetch normalized odds, and analyze opportunities. Minor gaps exist, such as no dedicated event-detail endpoint or historical odds endpoint, but these are not severe for the stated purpose.