Robinhood Pro

Confluence Pro MCP

The Pro tier includes a standard MCP server (not tied to one editor) that streams graded alerts, gamma rails, and a Robinhood execution checklist. Use it in Cursor, Claude Desktop, or VS Code with an MCP extension. Pair with Robinhood’s official MCP for quotes and orders when your client supports it. Advisory only — you confirm every trade.

Connect with the hosted connector (no install)

The Pro MCP is fully hosted — no Python, no repo clone, no config files. On a paid Claude plan (Pro, Max, Team, or Enterprise), Claude supports custom connectors. Add one URL with your Pro key:

https://mcp.0dteconfluence.com/mcp?key=YOUR_cfl_KEY

In Claude: Settings → Connectors → Add custom connector → paste the URL → the Confluence tools appear in every chat. Your key scopes the connection to your account. Free Claude plans don’t include custom connectors — use Cursor or VS Code with the hosted URL below instead.

Compatible clients

Claude (Pro, Max, Team, or Enterprise) — Settings → Connectors → Add custom connector
Cursor — add the hosted URL to .cursor/mcp.json (see below)
VS Code — any MCP-capable extension pointed at the hosted URL
Robinhood app — no MCP required; use #alerts-pro Discord backup + playbook

What you get

Pro API key (cfl_…) on the success page after checkout
25+ MCP tools — alerts, rails, tape, morning desk, market clock, IV skew, pin, GEX, expected move, RV regime, SPY/QQQ divergence, replay, tradeability gate, Robinhood entry plan, brackets, plus Quant/Macro (path risk, CVD, VRP, index health, macro events, daily structure)
Pro filter — score ≥6/8 · 9:45 AM–3:45 PM ET (through force-flat)

Cursor & VS Code (hosted URL)

Cursor and VS Code MCP extensions accept a remote connector URL — same hosted server, no Python or server files. Add the block below to .cursor/mcp.json (Cursor) or your VS Code MCP config:

{
  "mcpServers": {
    "confluence-pro": {
      "url": "https://mcp.0dteconfluence.com/mcp?key=YOUR_cfl_KEY"
    }
  }
}

Restart the editor → enable the confluence-pro server. Your Pro key scopes the connection to your account. Pair with Robinhood’s official MCP (https://agent.robinhood.com/mcp/trading) for quotes and orders when your client supports it.

Session workflow

get_morning_desk + get_rails before the open
Swing / weekly: get_swing_structure (5–45 DTE walls — not 0DTE)
Macro overlay: get_cross_asset · get_major_news · get_yield_curve · get_fear_greed (context only)
On an alert: retrieve the record, verify current structure and fresh Tape, then check_alert_tradeable → plan_robinhood_entry. Pass the same alert_json to both checks/planning calls to retain that specific alert; otherwise each call retrieves the latest record.
Robinhood MCP (or app): chain → quotes → review → you confirm → order
After fill: format_bracket_plan with your entry premium

Numeric trapdoor and eligibility fields

get_latest_alert() returns trapdoor directly. list_alert_history(limit=50, min_score=6) returns today's records newest first in alerts, each with its own trapdoor. Match timestamp, symbol, direction, and level.
The score is a stored alert-time 0–100 value, not a live rescore. null means unscored/unavailable — never treat it as zero or a solid wall. There is no standalone tool for requesting a fresh trapdoor score at an arbitrary level.
lane is grade-based: A+ = Lane 1, B = Lane 2. eligible records whether that lane was open when the alert was generated, not whether Discord could post it or the setup is still valid now.
_pro_eligible / _pro_reason in the latest-alert response are separate record/date/grade checks against the current Pro window, normally 9:45 AM–force-flat (default 3:45 PM ET). The standard Lane 1 window ends at 11:10 AM; an afternoon A+ can therefore have eligible=false and _pro_eligible=true.

Neither flag checks intervening one-minute closes, prior stop-outs, positions, or re-entry eligibility. A card remains a timestamped observation, not a standing recommendation. See lane vs Discord windows and rolling OFI and snapshot freshness.

Planning validation + broker quoting

get_latest_alert and list_alert_history apply the Discord posting filters — windows, quality gates, and dynamic deduplication — with the same plain-text card format. These are filtered scanner records, not a per-message delivery receipt or a live position tracker.

check_alert_tradeable rejects missing/non-object alerts, an absent or unreadable session date, another session's alert, an unsupported grade or invalid score, score < 6/8, a closed Pro window, a missing/nonpositive/nonfinite invalidation level, or a direction other than CALL/PUT. A present trapdoor value must be valid 0–100; null remains unscored. The existing MCP fade-fragility veto still applies. Discord separately filters fragile fades/reclaims; supplying custom JSON does not rerun the full scanner or Discord filters.

A passing planning gate is necessary, not sufficient, for acting on a setup. It does not regrade the candle or current flow, verify survival of the structural stop, check broker positions, or impose a maximum age in minutes on same-day alerts. No automatic re-entry follows from tradeable: true. Failed gates return a rejection, not an execution checklist or bracket targets.

plan_robinhood_entry then returns the advisory checklist — ~0.40–0.55 delta, spread ≤10% of mid (≤12% pre-9:45), and entry priced from Robinhood’s high_fill_rate_buy_price (not a guessed ask or passive mid). Exits use low_fill_rate_sell_price when available. Bracket defaults: scale toward structure, −25% premium cap, force-flat from get_market_clock.

1. check_alert_tradeable  → tradeable must be true
2. get_option_quotes      → high_fill_rate_buy_price = your buy limit
3. review_option_order    → fees / collateral / order_checks
4. place_option_order     → you confirm
5. format_bracket_plan    → +25% / −25% (or structural) on filled qty

Discord backup

#alerts-pro pings Pro members on mobile. MCP is the primary desk workflow when you're at the computer.

Install guide above · questions: [email protected]