MCP Integration · Beta

Use OptionsBell inside Claude

Connect OptionsBell as a Model Context Protocol server in Claude Desktop, Claude Code (CLI) or claude.ai. Ask natural-language questions about unusual options activity on 7,000+ US stocks - Claude fetches the data automatically and answers with the actual prints.

13 toolsStreamable HTTPRevocable connector URLsPrefer raw REST? See the API docs →

What you get

Once connected, Claude can answer questions like:

“What unusual put buying hit TSLA today?”
“Where has options flow shown up for 10+ consecutive days?”
“Which sectors is premium concentrating in this week?”
“Show me stocks with put IV rank above 0.8 - and pull the biggest prints on each.”
“How has flow on NVDA developed over the last month?”

No browser tabs, no copy-paste, no API client. Just questions and answers backed by the same data that powers the alerts.

Setup - choose your path

Four ways to connect Claude, in order of simplicity:

Recommended

Claude Desktop with a personal connector URL

Generate a URL once, paste it into Claude Desktop's config. No API key handling, fully revocable.

Open Settings → Claude Connectors
Click Generate connector URL (name it, e.g. "MacBook")
Copy the URL - it looks like https://optionsbell.com/u/mct_xxx/mcp
Claude Desktop → Settings → Developer → Edit Config → add it as the url field
Fully quit Claude Desktop (Cmd+Q on Mac), reopen - the tools icon shows the connection

{
  "mcpServers": {
    "optionsbell": {
      "url": "https://optionsbell.com/u/mct_xxx/mcp"
    }
  }
}

Claude Desktop with your raw API key

Prefer the key directly? Paste this into claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "optionsbell": {
      "url": "https://optionsbell.com/mcp",
      "headers": {
        "X-API-Key": "sms_your_key_here"
      }
    }
  }
}

Claude Code (CLI) - one command

Skip the JSON editing entirely. With your connector URL:

claude mcp add --transport http \
  optionsbell \
  https://optionsbell.com/u/mct_xxx/mcp

Verify with claude mcp list. Tools are available in the next chat session.

claude.ai (web) - custom connector

On Pro/Team accounts: Settings → Connectors → Add custom connector:

Name: OptionsBell
Remote MCP server URL: your connector URL (https://optionsbell.com/u/mct_xxx/mcp)
Leave OAuth Client ID and Secret empty → Add
Start a new chat - the tools menu shows the connection

Available tools

Claude invokes any of these when relevant to your question:

get_unusual_activity

Contract-level unusual activity scan with full filters

get_symbol_flow

Every unusual contract on a single ticker

get_top_prints

The day's biggest bets, ranked by premium

get_flow_history

Per-symbol EOD unusual-flow series for back-tests

get_flow_streaks

Symbols with N+ consecutive days of unusual flow

get_expiry_concentration

Premium along the DTE axis (event bets vs. positioning)

get_flow_sentiment

Bullish/bearish classification with 0-9 strength

get_iv_rank

IV rank & percentile vs. rolling history

get_oi_changes

Day-over-day open-interest gainers/losers

get_sector_flow

Which sectors the unusual premium concentrates in

get_market_regime

Unusual-flow breadth score & regime label per day

get_dataset_stats

Available date ranges & coverage discovery

ping

Liveness check, no key required

Cost & usage

MCP tool calls count 1:1 against your API rate limits - the same per-minute and per-day budget as direct REST requests (Pro: 30/min, 2,000/day). A typical research session uses 3-8 tool calls. Requires an active subscription; contract-level tools work on any paid plan, derived analytics need Pro.

FAQ

Where is my API key stored?

With a connector URL: nowhere on your machine. The URL resolves to your key on our server - your client config only holds the URL. With the raw-key setup, the key lives in your local Claude config file.

What happens if I lose my laptop or leak a connector URL?

Revoke that URL in Settings → Claude Connectors. It stops working immediately; your API key and other connectors stay untouched.

Can I generate multiple connector URLs?

Yes - up to 10 active ones, each with its own name (e.g. 'MacBook', 'Work'). Revoke them independently.

Does this work with Cursor, Cline, or other MCP clients?

Any client that speaks MCP over Streamable HTTP works. Point it at your connector URL, or at https://optionsbell.com/mcp with an X-API-Key header.

Why is it labeled Beta?

The tool set and response shapes may still evolve. The underlying REST API is stable; breaking MCP changes will be announced.

Get started in 60 seconds

Already a subscriber? Generate your connector URL now. Otherwise grab a plan and connect.

Generate connector URL See pricing REST API docs →