Options MCP Server

Option Chain MCP server

Local serverstdio

What is the Options MCP server?

Option Chain MCP server. That is what the options mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This Model Context Protocol (MCP) server gives AI assistants the tools to research options, without any ability to place trades:

  • Strikes are pre-filtered to a configurable percentage band around spot
  • Dead contracts are dropped (volume > 0 OR open_interest > 0 and bid/ask > $0.10)
  • A "significant strikes" pass keeps round-numbered strikes at distance and finer-grained strikes near the money — mimicking how a human trader actually reads a chain
  • Only the fields a research workflow needs are returned (no exchange codes, no raw timestamps, no boilerplate)
  • Read-only by design. — No place_order, no close_position, no exercise_options_position. Point an LLM at it without worrying about hallucinated trades
  • Provider-pluggable. — Tradier and Alpaca behind one identical tool surface. Swap with one env var; if one provider's data goes stale or the account expires, fall over to the other without changing prompts or client config

The tools it exposes

The server publishes 9 tools. What each one is for:

  • Read — only by design.** No place_order, no close_position, no exercise_options_position. Point an LLM at it without worrying about hallucinated trades
  • Provider — pluggable.** Tradier and Alpaca behind one identical tool surface. Swap with one env var; if one provider's data goes stale or the account expires
  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%\Claude\claude_desktop_config.json
  • Alpaca — ALPACA_API_KEY_ID, ALPACA_SECRET_KEY
  • Field — Tradier
  • open_interest — Returned natively
  • Requirements — The Requirements tool exposed by this server
  • Deploy — The Deploy tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at wrangler on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: TRADIER_TOKEN, ALPACA_API_KEY_ID, ALPACA_SECRET_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • A Cloudflare account on any paid Workers plan (Durable Objects are used for MCP session state) - Wrangler authenticated: npx wrangler login - A KV namespace bound as OAUTH_KV (create with npx wrangler kv namespace create OAUTH_KV and paste the ID into wrangler.jsonc)

How it compares

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Options's toolset — Read, Provider, macOS and 6 more — is a fair guide to whether it matches your workflow. It is maintained by blake365; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Options.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Readonly by design.** No place_order, no close_position, no exercise_options_position. Point an LLM at it without worrying about hallucinated trades.
Providerpluggable.** Tradier and Alpaca behind one identical tool surface. Swap with one env var; if one provider's data goes stale or the account expires, fall over to the other without changing prompts or client config.
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
AlpacaALPACA_API_KEY_ID, ALPACA_SECRET_KEY
FieldTradier
open_interestReturned natively
RequirementsThe Requirements tool exposed by this server.
DeployThe Deploy tool exposed by this server.

How to install the Options MCP server

{
    "mcpServers": {
        "options-chain": {
            "command": "node",
            "args": [
                "/Full/Route/to/Folder/options-chain/build/index.js"
            ],
            "env": {
                "TRADIER_TOKEN": "your_tradier_sandbox_token"
            }
        }
    }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • A Cloudflare account on any paid Workers plan (Durable Objects are used for MCP session state) - Wrangler authenticated: npx wrangler login - A KV namespace bound as OAUTH_KV (create with npx wrangler kv namespace create OAUTH_KV and paste the ID into wrangler.jsonc)
VariableDescriptionRequired
TRADIER_TOKENCredential the server authenticates with.Yes
ALPACA_API_KEY_IDCredential the server authenticates with.Yes
ALPACA_SECRET_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Options to Read.
  • Use Options to Provider.
  • Use Options to macOS.

Frequently asked questions

The server pre-filters chains server-side: only strikes within a configurable percentage of spot, with real volume/bid/ask, and a "significant strikes" pass are returned. This reduces token usage by 20–40× compared to raw API calls. It is also read-only (no trading endpoints) and supports remote OAuth deployment.