PropProfessor MCP
Provides tools to query MLB sports screen data from PropProfessor, including ranked screens, validated positive EV candidates, and sharp plays.
Provides tools to query NBA sports screen data from PropProfessor, including ranked screens, validated positive EV candidates, and sharp plays.
Provides tools to query NHL sports screen data from PropProfessor, including ranked screens, validated positive EV candidates, and sharp plays.
Provides tools to query UFC sports screen data from PropProfessor, including ranked screens, validated positive EV candidates, and sharp plays.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PropProfessor MCPget NBA moneyline odds"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PropProfessor MCP ── Sharp Money Intelligence for AI Agents
PropProfessor MCP is a Model Context Protocol server that lets AI agents see what the sharpest sportsbooks are doing. It screens 36 books across 10 leagues, detects coordinated sharp movement, surfaces steam moves and line lags, and explains the consensus — so you can decide what to bet, not be told.
Connect it to Claude Desktop, Cursor, Cline, Hermes, or any MCP client. Requires a PropProfessor account.
Honest scope — no profitability claim: PropProfessor MCP is a sharp-signal DISCOVERY and RATING tool.
tier/kaiCall/edge/screenScoreare signal-quality ratings, not win-probability predictions. Profitability is UNPROVEN — no settled-results backtest has been published yet. Use it to find candidate plays and validate them yourself; do not treat outputs as a guaranteed winning system. The ranking pipeline surfaces what sharp books are doing; the betting decision stays with you.
🚀 Overview
Your AI agent gets 31 tools that surface the same signal feed professional bettors use:
Screen & rank — query live odds across 36 sportsbooks, ranked by consensus edge and movement
Detect sharp coordination — Pinnacle, Circa, BookMaker, and BetOnline moving together? That's a signal
Explain the "why" — every play comes with a human-readable rationale: what moved, on which books, over what timeframe
Natural language routing — agents call
ask("best plays on Fliff tonight")and get routed to the right tool automatically
The pipeline extracts odds, hydrates line history, ranks by movement quality + consensus strength, assigns a tier and risk score, and returns everything your agent needs to present an informed recommendation. The betting decision stays with the human.
Related MCP server: RDF Explorer
⚡ Quickstart (30 seconds)
Install:
npm install -g propprofessor-mcp(or clone +npm installfor dev)Wire your MCP client — pick your client below:
Claude Desktop (
claude_desktop_config.json):{ "mcpServers": { "propprofessor": { "command": "pp", "args": ["--mcp"] } } }Cline (
cline_mcp_settings.json):{ "mcpServers": { "propprofessor": { "command": "pp", "args": ["--mcp"], "env": {} } } }Cursor — Settings → Features → MCP Servers → Add:
Name: propprofessor Type: command Command: pp --mcpContinue.dev (
~/.continue/config.json):{ "experimental": { "mcpServers": { "propprofessor": { "command": "pp", "args": ["--mcp"] } } } }Hermes (
~/.hermes/config.yaml):mcp_servers: propprofessor: command: pp args: [--mcp]Auth (one-time):
node scripts/pp-login.js— opens a browser for PropProfessor login and persists cookies for the server to use.Ask your agent: "What are tonight's sharpest plays on Fliff?"
That's it — your agent now sees 31 tools.
Verify your install:
npm run install:verifyruns the non-API test suite (53 tests, no credentials needed).
CLI — pp
PropProfessor ships with a fast, standalone CLI that calls handlers directly — no MCP server needed.
npm install -g propprofessor-mcp
pp scan mlb tennis -M supportive -n318 commands for scanning, validation, setup, and logging:
Command | Description |
| Find plays across leagues |
| Filter by movement (clean, bouncy, adverse) |
| Quick scan (5 fastest leagues) |
| Only BET verdict plays |
| Validate a specific play |
| Get full game details |
| Player context + injury/risk flags |
| Compare prices across books |
| Log a pick |
| Recent pick history |
| Ranked plays for a league |
| Fantasy optimizer props |
| Today's slate + pending picks |
| Auth + backend health check |
| MCP server (stdio) — connect your AI agent |
| One-command setup (Node check + auth + doctor + config) |
| Browser login to PropProfessor |
| Full diagnostic check |
MCP mode: pp --mcp runs as an MCP stdio server. Connect it to Claude Desktop,
Cursor, Cline, or any MCP client. Pass --mode full for the full 31-tool surface.
Quick start (installed globally): pp --mcp — works if you've run npm install -g propprofessor-mcp. No path needed.
Development/clone setup: use the full path — node /path/to/scripts/propprofessor-mcp-server.js — see MCP Client Setup below.
All commands support -j/--json for piping and --no-color for CI/Telegram output.
Example output (scan filtered by supportive movement):
MLB › Moneyline (2)
Houston Astros @ +127 | TIER 1 ● BET
1.9% · clv +4¢ · mv supportive_bouncy · 5 books
Chicago White Sox vs Houston Astros Fri, Jul 24, 6:40 PM
Tennis › Total Games (1)
Under 21.5 @ -104 | TIER 1 ● BET
3.4% · mv supportive_clean · 16 books
Avanesyan vs Oliynykova Fri, Jul 24, 7:00 AM📊 Backtesting
PropProfessor includes a backtest runner that prints settled-pick performance across any date range.
# Show last 30 days of settled picks
node scripts/backtest-runner.js --days 30
# Show a specific date range
node scripts/backtest-runner.js --from 2026-06-01 --to 2026-07-20
# Or use the installed binary
pp-backtest --days 30The runner reads from ~/.propprofessor/picks.json — the same file used by pp log and pp picks. It shows total picks, settled records, win rate, P&L, and breakdowns by tier and league. It never fabricates ROI. If no settled picks exist in the range, it says so honestly.
🏛 Architecture
PropProfessor MCP follows a layered data pipeline:
API Layer
PropProfessor Backend — authenticated REST API for live odds, line history, and fantasy data
ESPN Integration — live scores for tennis time correction and game verification
X / Google News — player context (injury news, tweets) for bet validation
Ranking Pipeline (Node.js)
Extract — parse raw odds payloads from the screen API, expand multi-book selections
Hydrate — enrich each row with 12-hour odds history via the backend API (cached cross-call with 5-min TTL)
Rank — score by consensus edge (% advantage over sharp consensus), CLV proxy (opening vs current line movement), and league-specific market priorities
Tier — assign TIER 1–4 based on movement grade (green/yellow/red) × risk score (1–10) × sharp book confirmation, with hysteresis to prevent thrashing
Format — output at three verbosity levels:
minimal(plain English),standard(tier/edge/risk/rationale),full(raw movement data)
MCP Server (stdio)
JSON-RPC over stdio — standard MCP transport with Content-Length framing (NDJSON optional)
31 tools — organized into situational, analytical, and research tiers
Server-side validation — enforces input schemas at the server, not trusting the client
Categorized errors — auth, backend, transport, validation, internal — each with structured recovery hints
Data Flow
flowchart LR
subgraph BOOKS["36 Sportsbooks"]
B1[Pinnacle]
B2[Circa]
B3[BookMaker]
B4[BetOnline]
B5[NoVigApp]
B6[Fliff]
BN[...30 more]
end
API[PropProfessor API]
subgraph PIPE["Ranking Pipeline"]
E[Extract odds]
H[Hydrate with line history]
R[Rank by movement + consensus]
T[Tier + risk score]
end
subgraph OUTPUT["31 MCP Tools"];
QS[quick_screen]
T[today]
SB[smart_bet]
VP[validate_play]
ASK[ask]
OTH[...25 more]
end
CLIENT[Your AI Agent<br/>Claude / Cursor / Cline / Hermes]
BOOKS --> API --> PIPE --> OUTPUT --> CLIENT
CLIENT -. "you decide what to bet" .- BOOKS🛠 Getting Started
Quick Start
git clone https://github.com/j17drake/propprofessor-mcp.git
cd propprofessor-mcp
npm install
npm link
pp-query init # auth + verification + config — all at oncepp-query init checks Node version, opens PropProfessor login if needed, runs doctor, and prints ready-to-paste MCP config for your client. Or do it step by step:
pp-query login # browser login
pp-query doctor # verify everything worksRequires a paid PropProfessor account. That's it — you're ready to connect your AI agent.
MCP Client Setup
Add to your client's MCP config:
{
"mcpServers": {
"propprofessor": {
"command": "node",
"args": ["/path/to/propprofessor-mcp/scripts/propprofessor-mcp-server.js"],
"env": {
"PROPPROFESSOR_MCP_NDJSON": "true",
"AUTH_FILE": "/path/to/.propprofessor/auth.json"
}
}
}
}Replace /path/to/ with your actual install path (e.g. /Users/you/projects/propprofessor-mcp). Supports Claude Desktop, Cursor, Cline, Zed, Continue.dev, Windsurf, and any other stdio-based MCP client. See each client's docs for where MCP config lives.
For short-lived one-off sessions:
{ "command": "npx", "args": ["-y", "propprofessor-mcp"] }Works out of the box — no git clone needed. Requires a PropProfessor account.
For headless/CI environments (no Chrome):
Set the PROPPROFESSOR_COOKIES env var with your PropProfessor cookies exported as JSON. This bypasses the CDP/Chrome auth path entirely:
{
"mcpServers": {
"propprofessor": {
"command": "npx",
"args": ["-y", "propprofessor-mcp"],
"env": {
"PROPPROFESSOR_COOKIES": "[{\"name\":\"__Secure-next-auth.session-token\",\"value\":\"...\",\"domain\":\".propprofessor.com\"}]"
}
}
}
}Hermes Agent
If you use Hermes Agent:
make install # register MCP server + install default configOr manually: add propprofessor to your mcp_servers in config.yaml. The get_started tool provides on-demand workflow guidance.
Optional: Sharp-money alert cron
make install-cronRuns hourly, delivers TIER 1 plays to your home Telegram channel.
🎯 The Natural Language Flow
ask is a query router — it parses natural language and returns a suggested tool + args, but it does NOT execute the tool. Your agent calls ask to figure out what to do, then makes the actual call:
You: "Tell me the best plays on Fliff tonight"
Agent: ask({ query: "best plays on Fliff tonight" })
→ { parsed: { book: "Fliff" }, suggestedTool: "quick_screen", suggestedArgs: { books: ["Fliff"] } }
Agent: quick_screen({ books: ["Fliff"] })
→ [ranked plays with odds, edge, tier, risk, rationale — all on Fliff]You say | Agent asks | Returns |
"best plays on Novig" |
| Playable bets with player context |
"what should I bet today" |
| TIER 1 & TIER 2 across major leagues |
"Tatum over 29.5 points" |
| Injury/news risk check |
"show me MLB sharp plays" |
| Multi-sharp consensus plays |
"line shop Celtics ML" |
| Best price across 36 books |
"validate that Warriors spread play" |
| BET/CONSIDER/PASS verdict |
📊 Available Tools
Quick Situational Checks
Tool | What it does |
| Parse natural language query into the right tool + args (router, does NOT execute — agent calls the suggested tool separately) |
| One-call daily briefing: sharp slate + your pending picks + recent stats |
| Returns recommended workflow for casual/intermediate/sharp users |
| List available markets for a sport, with per-book market names (e.g. Soccer → Draw No Bet) |
| Best plays on any book with sharp consensus + player context |
| One-call: play details + validate_play verdict + best price + staking |
| Injury/availability check on a specific player |
| One-call verdict: re-fetches odds, checks injury news, returns BET/CONSIDER/PASS + playId + drift detection |
| Starting pitchers, park factor, hourly weather, lineup lock for an MLB game |
| Line-shop across all books for the best execution price |
| Auth freshness and endpoint connectivity |
Deeper Signal Analysis
Tool | What it does |
| Multi-window (1h–48h) sharp movement — is the move sustained? |
| Full ranked data for a (league, market) pair with consensus and movement metadata |
| Consolidated ranked list across multiple leagues in one call |
| Sport-specific ranking weights and sharp-book reference sets |
| Line movement and steam move alerts since last check |
| Fast +EV discovery — validate on |
| UFC card shortlist with official plays, best looks, and pass notes |
| Sharp action $ volume + per-side odds range per game (the signal the +EV feed hides) |
Research & Bet Management
Tool | What it does |
| Line history for specific game IDs |
| Fractional Kelly sizing (TIER 1: 2%, TIER 2: 1% of bankroll) |
| DFS-style fantasy picks (PrizePicks, Underdog — requires Fantasy Optimizer sub) |
| Track your own bet outcomes |
| Validate + log a play in ONE call; returns a pickId for settlement |
| View logged bets and win rate / P&L |
| Hide/unhide bets on the fantasy table |
| Reset tier trajectory tracking for a fresh session |
Output Tuning
Every tool accepts:
Parameter | Values | What it does |
|
| Controls explanation depth and field output |
|
| Strips line history and debug payloads — reduces response size by ~90% |
|
| Return only specified fields per row |
quick_screen additionally accepts:
Parameter | Values | What it does |
|
| Date filter. |
|
| Max plays shown per game in |
|
| When |
|
| Run player_context research on each returned play and attach |
|
| Max final plays to run research on. Bounds payload size on large scans. |
Player research is ON by default in
quick_screen(passincludeResearch: falseto disable). It's scoped to the final returned plays and de-duplicated per game, soresearchalways maps 1:1 to what you got back. On a huge unfiltered scan, lowerresearchLimitor useliteif the response nears the transport cap.
cardWindowhonesty: whentodayis alive and next-day rows are merged, the response reportscardWindow: "today"(not tomorrow's date) plusnextDayMerged: trueandnextDayDate. Earlier builds mislabeled this as tomorrow — that bug is fixed.
Tier consistency: as of 2.8.x,
tierCacheis cleared at the start of every MCP screen call (quick_screen,screen_ranked,validate_play). A given play's tier is therefore stable within a call and recomputed fresh per call — no cross-call drift from stale hysteresis state.
verbosity: minimalreturns a plain-English summary string WITH a structuredplaysarray — agents get both human-readable text and machine-parseable data in one call. Each play in the array includesleague,market,game,selection,odds,confidenceTier,edge,startCST,movementDisposition, andscreenScore.
Tool Surface Modes
Set PROPPROFESSOR_MCP_MODE at server boot to control how many tools the agent sees on tools/list:
Mode | Default | Tools exposed | Best for |
| ✅ yes | 15 | Recommended for most users. Covers the full workflow (discover → drill-down → validate → track) without overwhelming the tool catalog. |
| no | 31 | Power users — every discovery, screen, research, and admin tool. More tools but more noise for the agent to reason about. |
Lite mode exposes: ask, smart_bet, quick_screen, today, find_best_price, validate_play, get_play_details, player_context, log_pick, get_pick_history, resolve_pick, get_market_registry, place_bet, sharp_alerts, health_status.
The tools/list response always includes a _meta block so agents can tell which mode is active:
{
"tools": [...],
"_meta": { "mode": "full", "toolCount": 31, "liteToolCount": 15, "fullToolCount": 31 }
}Tool Categories
Every tool carries a category field that groups it by purpose — agents can use this to mentally cluster the surface rather than reading 29 individual descriptions:
Category | Count | Purpose | Tools |
| 6 | Find plays (scout, multi-league, DFS, +EV) |
|
| 5 | Score / rank plays for a target book |
|
| 3 | Deep dive on a specific play |
|
| 3 | Context data (player news, game weather, alerts) |
|
| 4 | Personal bet log |
|
| 2 | Bookkeeping (cache, hidden bets) |
|
| 3 | Server info / workflow guides |
|
Canonical vs Deprecated Param Names
A handful of params accept both a clean canonical name and a legacy alias — every existing call site keeps working, and new code can use the cleaner names:
Canonical (prefer) | Deprecated alias | Where |
|
| 13 tools — |
|
|
|
|
|
|
Deprecated aliases are documented in each schema's description field and are normalized to the canonical key at dispatch time. No code change required for existing callers.
🧪 How the Ranking Works
The pipeline grades every play in 5 steps:
Movement grade — green (all sharp books aligned), yellow (some signals, some not), red (adverse)
Risk score (1–10) — weighted from movement quality, consensus count, CLV strength, execution quality, and freshness
Tier assignment — lookup table: green + low risk → TIER 1, green-yellow + moderate → TIER 2, yellow → TIER 3, red → TIER 4
Hysteresis — a play doesn't thrash between TIER 1 and TIER 3 on small odds changes; tier trajectory is smoothed
Sharp cross-reference — verifies target-book moves independently against non-target sharp books
Tier system:
Tier | Label | Meaning | Stake |
TIER 1 | Lock | Green movement, risk 1–3, BET call. All signals aligned. | 2% of bankroll |
TIER 2 | Value | Yellow-green movement, risk 3–5, BET or CONSIDER. Solid play. | 1% of bankroll |
TIER 3 | Speculative | Yellow movement, risk 5–7, usually CONSIDER. | Skip or 0.25% max |
TIER 4 | Avoid | Red movement, risk 7+, PASS call. Do not bet. | 0% — no exceptions |
Full methodology, weight tables, and the tier assignment lookup in docs/METHODOLOGY.md. Backtesting results in docs/BACKTESTING.md.
🔌 Integrations
See Quick Start for Hermes Agent setup. The MCP is self-documenting — agents call get_started to discover the right workflow.
Discord / Telegram Alerts
The Positive EV Command Center is a companion project that monitors PropProfessor for high-EV slips and plays, then pushes them to Discord and Telegram in real-time. It uses the same auth session and API client.
CLI
pp-query is a standalone CLI for one-off queries without an MCP client:
pp-query screen --league NBA --market Moneyline
pp-query recommended --leagues NBA,MLB
pp-query login
pp-query doctor📈 Backtesting
TL;DR: The infrastructure is in place. Real outcome data hasn't accumulated yet.
Two paths to validate the signal:
1. Synthetic engine validation — runs generated scenarios (sharp_move, stable_no_edge, adverse) through the full pipeline to confirm the tier system actually differentiates quality:
node scripts/backtest-synthetic.js2. Real outcome backtest — snapshot-based, since the PropProfessor API does not serve historical settled results. Take a pre-game odds snapshot daily, then resolve outcomes as games settle:
# capture today's recommended plays
node scripts/daily-snapshot.js
# after games settle, apply win/loss/push via CSV
node scripts/resolve-outcomes.js --csv results.csv
# compute P&L, ROI, Sharpe, max drawdown from resolved data
node scripts/backtest.js --metrics data/snapshots.jsonlThe pipeline (daily-snapshot.js → settle games → resolve-outcomes.js →
backtest.js --metrics) is built and tested (8 pipeline tests, 0 fail). What's
missing: real settled-results data. The synthetic tier-validation run shows
a TIER 1 hit rate of 51.4% over N=296 simulated samples — these validate
the ranking engine, they do NOT prove profitability.
Honesty: tier/kaiCall/edge/screenScore are signal-quality ratings, not win-probability predictions. Profitability is UNPROVEN — no settled-results backtest has been published yet. The system surfaces what sharp books are doing; it doesn't come with a bundled historical results feed. Don't trust a win rate you can't trace to settled bets. See docs/BACKTESTING.md.
🔧 Troubleshooting
Symptom | Likely cause | Fix |
| Auth token expired or invalid | Run |
| Upstream API is down or rate-limited | Wait ~30s for the half-open retry; if persistent, run |
| Wrong parameter name or type | Use the canonical param names (e.g. |
Empty results from | No sharp consensus plays on that book+league combo right now | Remove |
| Market name mismatch per league | Call |
First | Multi-league fan-out cache is cold | Normal. Subsequent calls with identical args return <5ms from the response cache |
Some tools are missing from | Server booted in lite mode | Set |
| Circuit breaker threshold exceeded | Increase |
Debug logging needed | — | Set |
Still stuck? Run pp-query doctor and open an issue with the output.
❓ FAQ
Does this tell me what to bet? No. It surfaces what sharp books are doing. The betting decision is yours.
Do I need a PropProfessor account? Yes. Live data requires a paid subscription at propprofessor.com.
What books does it cover? 36 sportsbooks across 10 leagues. Sharp cross-reference: Pinnacle, Circa, BookMaker, BetOnline.
Is it free? Code is MIT-licensed. Data requires a paid PropProfessor subscription. No paid tier of the MCP itself.
Can I run it without an MCP client? Yes — pp doctor is a standalone CLI.
What if I find a bug? Run pp doctor first, then open an issue.
⭐ Support
This is free, MIT-licensed software. If it saves you time or makes you money:
⭐ Star the repo — helps others find it
🐛 Open an issue when you find a bug
💸 Sponsor on GitHub — funds ongoing development
No paid tier. No upsell. The whole codebase is open and the priority is making it better for the people who use it.
🔧 For Maintainers
npm test # 1396 tests, 0 failures
npm run test:coverage # ~82% statements
npm run lint # clean
npm run format:check # clean (npm run format to fix)
npm run check:version # verifies package.json ↔ CHANGELOG
npm run smoke:live # end-to-end live smoke (requires auth.json)Release: push a v* tag → CI runs lint + tests on Node 20 + 22 → auto-creates the GitHub release.
📚 Docs Index
Doc | What it covers |
Quick start, auth, CLI reference, tool list, tuning, architecture | |
Environment variables, book config, token compression | |
How to add a tool, testing, PRs | |
Release process, smoke tests | |
Full ranking math: movement grade → risk score → tier + hysteresis | |
Synthetic & real-outcome backtest methodology | |
Full system prompt for AI agents using PropProfessor | |
5 patterns every AI agent needs (cheat-sheet) | |
JSON response shapes for all tools | |
Hermes Agent integration skill | |
Response size, latency benchmarks, token usage | |
Which markets each book supports, per league | |
Full release history | |
AI agent discovery file (compact overview for LLMs) |
📝 License
MIT. PropProfessor is a paid service; this MCP is an unofficial client built by j17drake, not affiliated with PropProfessor.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).Last updated1193Apache 2.0
- Alicense-qualityFmaintenanceThe Model Context Protocol (MCP) server provides a conversational interface for the exploration and analysis of RDF Turtle Knowledge Graph in Local File mode or SPARQL Endpoint.Last updated54MIT
- Apache 2.0
- Alicense-qualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.Last updatedMIT
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Local-first RAG engine with MCP server for AI agent integration.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jbdrak/propprofessor-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server