Using Claude Code and Mboum's MCP Server to Analyze Options Chains Conversationally

You can ask an AI assistant about options without writing a script. Mboum runs a Model Context Protocol (MCP) server that lists its market data endpoints as tools. Connect it to Claude Code, and the assistant calls the API for you whenever a question needs an options chain, an IV rank or a day's unusual activity. This guide sets up the connection, gives four prompts that work well, and explains where the tools stop.

Prerequisites

  • Claude Code installed in your terminal.
  • A Mboum API key. Create one on the API Tokens page of your account.
  • Any plan. The MCP server works on every plan, including Free, and every Mboum plan includes options data.

There is no separate charge for the MCP server. Each tool call is a normal API request and counts against your monthly allowance at the endpoint's weight. Listing the tools does not count.

Connect Claude Code

The server address is https://api.mboum.com/mcp. Replace the key and run:

claude mcp add --transport http mboum https://api.mboum.com/mcp \
  --header "Authorization: Bearer YOUR_MBOUM_API_KEY"

claude mcp list

The second command lists your servers and shows whether mboum connected. Inside Claude Code, /mcp shows the same server. Keep your key out of any config file you commit to a shared repository.

The tools that matter for options

  • get_options_chain (weight 2): calls and puts for one underlying and one expiration, plus the list of available expirations. Each contract has strike, bid, ask, lastPrice, volume, openInterest, impliedVolatility and inTheMoney. The response also carries a quote for the underlying.
  • get_unusual_options_activity (weight 2): contracts trading at high volume relative to open interest, 20 per page. Rows include volumeOpenInterestRatio, volatility, delta and daysToExpiration.
  • get_iv_rank_percentile (weight 2): one-year IV rank and IV percentile for symbols on the day's most active options list, 20 per page.
  • get_quote and get_price_history (weight 1 each) for the underlying price and daily candles.

Four prompts to try

1. Read a chain

Using Mboum, get the SPY options chain for the nearest expiration. Show the
five calls and five puts with the highest open interest: strike, bid, ask,
volume, open interest and implied volatility.

This costs 2. Because the chain response includes the underlying quote, the assistant can also say how far each strike sits from the current price. Tickers with many strikes, such as SPY, can trigger the shortening described below.

2. Find elevated IV

Using Mboum, get today's IV rank and IV percentile list for STOCKS. Which
five symbols have the highest IV rank? Include options volume.

This costs 2 per page. The list covers symbols on the day's most active options list, not every stock, so a quiet ticker will not appear.

3. Review unusual activity

Using Mboum, pull unusual options activity for TSLA. Which contracts have a
volume to open interest ratio above 5? Show strike, expiration, delta,
volatility and days to expiration.

This costs 2. The data does not say who bought or sold, or whether a trade opened or closed a position. If the assistant describes a contract as "bullish" or a "sweep", that is its own inference.

4. Pick an expiration

Using Mboum, find the AAPL expiration closest to 30 days from today and show
the calls within 5% of the current price.

The chain tool takes an expiration as a Unix timestamp from the expirationDates list in a previous response. A request for a specific date can therefore take two calls, one to read the list and one to fetch the chosen expiration, for a total of 4.

What a chain contract looks like

This is one call contract from the docs example response:

{
  "contractSymbol": "AAPL230811C00050000",
  "strike": 50,
  "lastPrice": 129.3,
  "volume": 2,
  "openInterest": 4,
  "bid": 127.5,
  "ask": 128.8,
  "expiration": 1691712000,
  "impliedVolatility": 7.26562591796875,
  "inTheMoney": true
}

Implied volatility is a decimal, so 0.30 means 30%. This deep in-the-money contract shows 7.27, or 727%. Illiquid contracts can show extreme values like this, so ask the assistant to ignore contracts with no volume.

Where the tools stop

Greeks. The chain tool returns implied volatility, not delta, theta or vega. Unusual-activity rows include delta. For full Greeks, call the REST endpoint yourself. GET /v3/markets/options has weight 2 and returns delta, vega and theta for every contract:

curl -H "Authorization: Bearer YOUR_MBOUM_API_KEY" \
  "https://api.mboum.com/v3/markets/options?ticker=AAPL"

See the endpoint docs for the parameters.

Shortened results. Long lists are cut before they reach the assistant. Most tools keep the first 50 entries, and price history keeps the most recent 120 bars. When that happens, the result starts with a "Shortened for length" note that names the list and how many entries it held. For a chain, the cut can drop strikes, so an answer such as "highest open interest" may rest on a partial list. Ask the assistant whether any result was shortened, and use the REST API when you need everything.

Best practices

  • Be specific. Name the ticker, the expiration and your thresholds. A vague question makes the assistant guess, and it may make several calls to answer.
  • Watch the calls. Claude Code shows each tool call. Check how many a prompt used, and compare your usage on the dashboard.
  • Verify before you act. An assistant can misread a field or round a number. Spot-check anything important against the REST response.
  • Protect the key. Anyone with your key can spend your allowance. If it leaks, revoke it on the API Tokens page and create a new one.

Data is for information only and is not investment advice.

Next steps

Get a free API key at mboum.com/pages/api, read the MCP setup guide for other clients, and browse every endpoint in the API documentation.