MCP server reference

The strike.trading MCP server is the product’s only API. The terminal uses the same handlers, so anything an agent can see or do, you can see in the terminal, and every agent action lands in the same log.


Endpoint	`https://mcp.strike.trading`
Transport	Streamable HTTP
Authorization	OAuth 2.1 through WorkOS AuthKit: authorization code with PKCE, client ID metadata documents, dynamic client registration, device flow
Tools	10 — four read the ladder, two place and cancel orders, four read your account
Resource	`ladder://{symbol}/{expiry}`, subscribable
Prompt	`trade_plan`
Tool schemas	`GET https://mcp.strike.trading/mcp/schema.json`

New here? Start with the quickstart on the Agents page, then read Authorization.

Conventions

JSON is snake_case. Times are RFC 3339 in UTC. Expiries are YYYY-MM-DD.
Ladder prices (above_price, below_price, unit_cost) are on a 0 to 1 scale per $1 of payoff.
Order prices (limit, net_price, entry_price, mark) are dollars per share, the way Tradier quotes them. One spread is 100 shares.
Every read result carries the snapshot_id of the ladder it was computed from. The action log records it too.

What the server will never do

It never recommends a trade, ranks trades, or tells an agent whether to hold a view. best_expression compares ways to express a view your agent already has. It never moves money and never changes limits: limits loosen only in the terminal.

These pages are generated from the same tool schemas the server serves, so they can’t drift from it.