fanduelapi-mcp
# fanduelapi-mcp
MCP server (stdio) for [FanDuel API](https://fanduelapi.com): FanDuel Sportsbook player props, line moves, game lines, +EV and arbitrage for Claude Desktop, Claude Code, Cursor, Codex, Windsurf, VS Code and any MCP client.
It is a small relay with no dependencies: each JSON-RPC message from your client goes to the hosted server at `https://fanduelapi.com/api/mcp` with your key, and the reply comes back on stdout. Use it when your client only speaks stdio; clients that support remote servers can use the URL directly (https://fanduelapi.com/mcp).
FanDuel API is an independent data service operated by Stunning Couches LLC. It is not affiliated with, endorsed by or sponsored by FanDuel.
## Use it
Free key, no card: https://fanduelapi.com/sign-up. Without a key the keyless tools still work.
Claude Desktop, Cursor and most clients (`claude_desktop_config.json`, `.cursor/mcp.json`):
```json
{
"mcpServers": {
"fanduelapi": {
"command": "npx",
"args": ["-y", "fanduelapi-mcp"],
"env": { "FANDUEL_API_KEY": "fd_..." }
}
}
}
```
Claude Code:
```bash
claude mcp add fanduelapi --env FANDUEL_API_KEY=fd_... -- npx -y fanduelapi-mcp
```
Codex (`~/.codex/config.toml`):
```toml
[mcp_servers.fanduelapi]
command = "npx"
args = ["-y", "fanduelapi-mcp"]
env = { FANDUEL_API_KEY = "fd_..." }
```
Then ask, for example: "Which NBA points props on FanDuel moved most in the last hour?" or "Show FanDuel prices above the fair price tonight."
## Tools
The tool list comes from the hosted server, so it stays current. On 15 November 2026 it was:
- No key: `search_docs`, `fetch_doc`, `search`, `fetch`, `get_sample_props`, `describe_signup`, `start_signup`, `finish_signup`, `get_onboarding_questions`, `send_feedback`.
- With a key: `list_props`, `line_move`, `prop_history`, `recent_changes`, `odds_board`, `game_report`, `positive_ev`, `arbitrage`, `compare_books`, `list_events`, watches, onboarding and subscription tools.
Check it with no key:
```bash
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_sample_props","arguments":{"sport":"nba"}}}' | npx -y fanduelapi-mcp
```
## Settings
| Variable | Default | Meaning |
| --- | --- | --- |
| `FANDUEL_API_KEY` | none | Your key. Sent as `Authorization: Bearer`. |
| `FANDUEL_MCP_URL` | `https://fanduelapi.com/api/mcp` | Upstream server. |
| `FANDUEL_MCP_TIMEOUT_MS` | `60000` | Per-request timeout. |
Calls spend credits like REST calls do; see https://fanduelapi.com/credits. When a plan's month runs out, the tool result says so with a one-click link for the person; the server never buys anything.
## Tests
```bash
npm test # against a local fake upstream
FANDUEL_LIVE=1 npm test # also checks the hosted server's keyless tools
```
## License
MIT
TDQS
Scored across 29 tools
Most tools target distinct resources (props, events, line history, EV, arbitrage, watch CRUD, billing), but there are outright duplicates: search_docs vs search and fetch_doc vs fetch are functionally the same pair, differing only in 'shape'. There is also mild overlap between list_events, odds_board and game_report (all can surface games/lines), so an agent must read descriptions carefully to pick correctly.
The dominant pattern is snake_case verb_noun (list_watches, get_subscription, cancel_subscription), but a substantial second family of bare-noun analytics names exists (line_move, prop_history, recent_changes, odds_board, game_report, positive_ev, arbitrage) plus bare verbs (search, fetch). Within-set pluralization is also odd (create_watches/get_watches vs get_subscription), so conventions are mixed though still readable.
At 29 tools this is a heavy surface for an odds API, and a meaningful share is not earning its place: two doc-search aliases, a three-step signup flow, and a separate cancellation trio. The domain is broad (odds data + billing + onboarding), but the set could be trimmed toward the 15-20 range without losing capability.
Coverage is strong: docs search, discovery (events/odds board/game report), prop data with history and change feed, analytics (EV, arbitrage, book comparison), watchlist CRUD, signup and subscription lifecycle, feedback and onboarding. Gaps are minor — no endpoint for enumerating stat types, players/teams, or managing watch notification delivery — and are workable around via existing filters.