Quant Data has a hosted MCP server that connects Claude to options flow data. To connect without code, add the Quant Data connector in Claude’s directory and sign in with your Quant Data account: there is no API key to copy. Then ask in plain English.
You need a Quant Data account with an active API subscription. The Quant Data API is $149.99 a month or $1,499.99 a year for every endpoint over REST and MCP.
The Quant Data MCP server is at https://api.quantdata.us/mcp and has 31 read-only tools. They cover sweeps, blocks, splits and single prints, gamma exposure, open interest, max pain, volatility and dark pool prints.
Checked on November 12 and 13, 2026. The tool list and every example result on this page were requested on November 12 by a script that called https://api.quantdata.us/mcp directly, not from inside Claude. Claude Code connected to that server and listed all 31 tools on September 22 and October 29, 2026; the config file on this page is the one from October 29. The Claude Desktop steps are the ones in our API overview of June 17, 2026; we did not repeat them for this page. We read the Quant Data page in Claude’s directory on November 13, 2026.
At a glance
Quant Data and Claude | |
What it is | A hosted MCP server, run by Quant Data at https://api.quantdata.us/mcp with 31 read-only tools: 30 data tools and a connection check |
Where to add it | |
What you can ask about | Options flow (sweeps, blocks, splits and single prints), gamma and other Greek exposure, open interest, max pain, volatility, stock prices, dark pool prints and news |
Coverage | 6,000+ tickers, from exchange-licensed data |
Which session | The latest trading session when a call has no |
What you need | A Quant Data account with an active API subscription. To connect by hand: Claude Code or Claude Desktop |
How Claude connects | The directory connector: add it and sign in, with no code. By hand in Claude Code: a config file with the server address (tested). By hand in Claude Desktop: a custom connector, with pictures in the API overview |
Sign-in | The directory connector: you sign in with your Quant Data account and there is no API key to copy (per the directory listing). Claude Code sends your Quant Data API key in an Authorization header. Per the API overview, the custom connector has you authorize with your Quant Data account |
Price | $149.99 a month or $1,499.99 a year for every endpoint over REST and MCP |
Limits | 240 requests per 60 seconds, plus a burst cap of 20 per second, with no monthly quota. One tool call is one request |
Read-only | Every tool reads data. None places a trade or changes your account |
Docs | |
Where to subscribe |
How do I connect Claude to options flow data with MCP?
To connect Claude to options flow data with MCP, add the Quant Data connector from Claude’s directory, or point Claude at the Quant Data MCP server by hand. MCP, the Model Context Protocol, is the open standard Claude uses to call outside tools. The three routes:
The Quant Data connector in Claude’s directory, with no code.
By hand in Claude Code, with a config file and your Quant Data API key.
By hand in Claude Desktop, with a custom connector (per our API overview).
How do I add Quant Data from Claude’s directory?
To add Quant Data from Claude’s directory, open the Quant Data page there, add the connector and sign in with your Quant Data account. The steps, from the directory listing:
Start with a Quant Data account that has an active API subscription (see the API plans).
Open the Quant Data page in Claude’s directory.
Add the connector from that page. If you are signed out of Claude, the button reads “Sign in to add”.
Connect by signing in with your Quant Data account, with no API key to copy.
Ask in plain English, for example “Where is SPX gamma exposure concentrated by strike?”
Requests count toward your API rate limit, and the connector is read-only.
What do I need to connect Claude to Quant Data?
To connect Claude to Quant Data you need two things, and a third to connect by hand:
A Quant Data account with an active API subscription.
A signed market-data subscriber agreement, for options data. Until you sign, options requests return the signing link.
To connect by hand, Claude Code or Claude Desktop. For Claude Code you also need your Quant Data API key, which you create on the API keys page in your Quant Data settings.
Illustration. These are routes 2 and 3 of the three, the two set up by hand. Route 1, the Quant Data connector in Claude’s directory, is not pictured.
How do I connect Claude Code to Quant Data?
Claude Code connects to the Quant Data MCP server with one environment variable and one config file. Steps 1 to 3 are the setup we tested.
Step 1: Put your API key in an environment variable
On macOS or Linux:
export QD_API_KEY="<your key>"
In Windows PowerShell:
$env:QD_API_KEY = "<your key>"
Step 2: Save the config file
Save this as quant-data-mcp.json. Claude Code fills in ${QD_API_KEY} from the environment, so the key is not saved in the file.
{
"mcpServers": {
"quant-data": {
"type": "http",
"url": "https://api.quantdata.us/mcp",
"headers": {"Authorization": "Bearer ${QD_API_KEY}"}
}
}
}
Step 3: Start Claude Code with the file
Run this in the same terminal as Step 1, from the folder that holds the file:
claude --mcp-config quant-data-mcp.json
Step 4: Check the connection
Our MCP Server docs suggest asking Claude to run qd_ping, the connection check, and they also give a one-line claude mcp add command for Claude Code. In our runs, Claude Code showed the Quant Data server as connected with 31 tools. When we called qd_ping directly on November 12, 2026, the server answered that it was alive.
How do I connect Claude Desktop to Quant Data?
Claude Desktop can connect to the Quant Data MCP server through a custom connector added by hand, an alternative to the directory connector. Our Quant Data API overview shows each click with a picture: under Customize, then Connectors, add a custom connector, enter Quant Data as the name and https://api.quantdata.us/mcp as the remote MCP server URL, then authorize with your Quant Data account when prompted.
What if Claude cannot connect, or Quant Data refuses a request?
When the Quant Data API turns a request down, the HTTP status code it returns says why. Three of them have a fix on your side:
Status | What it means | What to check |
HTTP 401 | Authentication failed: the API key is missing or invalid | In Claude Code: that the |
HTTP 403 | No active API subscription, or, on options requests, the market-data subscriber agreement is not signed | Whether your API subscription is active. For the agreement, the response carries the signing link |
HTTP 429 | You are over the request limit | Wait, then ask again. The API’s 429 response carries a Retry-After header with the seconds to wait |
To test the connection on its own, ask Claude to run qd_ping (Step 4 of the Claude Code setup). Per our MCP Server docs, a reply means the address and the key both work. The API docs’ Errors page lists the error codes.
Can Claude read options flow data?
Yes. Once Claude is connected to the Quant Data MCP server, two of its tools return the flow itself. Consolidated flow has one row per sweep, block or split; unconsolidated flow has one row per print on one exchange. For how the two differ, see Options Flow API: Consolidated and Unconsolidated Flow Data.
For ChatGPT, see Connect ChatGPT to Options Flow Data: Quant Data Plugin.
Illustration. Each tool call counts as one request against your API limit.
What can I ask Claude once Quant Data is connected?
Once Quant Data is connected, you can ask Claude about options flow, exposure, open interest, max pain, volatility, stock prices, dark pool prints and news, in plain English. Each row pairs a question with the Quant Data tool that holds the data and what that tool returned to our script for the November 12, 2026 session.
Ask | Quant Data tool | What came back |
“Where is SPX gamma exposure concentrated by strike?” | qd_get_exposure_by_strike | 601 rows, one per strike, with call and put exposure |
“Show the largest NVDA options sweeps of the session.” | qd_get_order_flow_consolidated | 10 rows, one per sweep, sorted by premium |
“What is the max pain strike for each SPY expiration?” | qd_get_max_pain_over_time | 34 rows, one per expiration, from November 12, 2026 to January 19, 2029 |
“Which TSLA contracts had the largest open interest increases?” | qd_get_open_interest_change | 15 rows, one per contract, with the previous and current open interest |
What does Claude get back from Quant Data?
Claude gets back text shaped like a CSV table from Quant Data: sometimes a few key=value lines, then a header row, then one row per strike, trade or time bucket.
Here is the SPX question as a tool call. We sent it to qd_get_exposure_by_strike after the close on November 12, 2026, with these arguments:
{
"ticker": "SPX",
"greekMode": "GAMMA",
"representationMode": "PER_ONE_PERCENT_MOVE",
"sessionDate": "2026-11-12",
"expirationDateRange": {"startDate": "2026-11-13"}
}
The last argument limits the result to expirations from November 13, 2026 on. We passed sessionDate to keep the example on one session.
Real response, session November 12, 2026 (the opening lines)
SPX.stockPrice=7592.06
ticker,strikePrice,callExposureSum,putExposureSum
SPX,200.0,0,0
SPX,400.0,0,-31949
SPX,600.0,0,-155028
The result has 601 rows, one per strike, and put values come back negative. Its three largest call values and three largest put values:
Rank | Call strike | callExposureSum | Put strike | putExposureSum |
1 | 7000 | 16,138,422,980 | 8000 | -17,295,662,610 |
2 | 7700 | 15,110,967,410 | 7000 | -8,306,141,418 |
3 | 8000 | 8,172,623,149 | 7600 | -7,912,887,515 |
Outside this range, the result’s largest values are calls at 7000 and puts at 8000.
The values are in dollars per 1% move, the representationMode the call asked for. The tool has two other modes, each on its own scale. For the same data over REST, see Gamma Exposure (GEX) API.
Does Claude get the current session or past sessions from Quant Data?
26 of the 31 Quant Data tools take a sessionDate: they use the latest trading session when a call leaves it out, and a past session when a call names one. Some return a snapshot: without it, Exposure by Strike, the tool in the SPX example, returns the latest snapshot of the current session. During the session, at 2:41 PM ET on November 12, 2026, an options flow request to the Quant Data API with no date returned that day’s rows.
History goes back up to 6 years, depending on the dataset. For past sessions over REST, see Historical Options Data API: Trade-Level Data, 50+ Filters.
Which Quant Data tools does Claude see?
Claude sees 31 Quant Data tools: 30 data tools plus qd_ping, a connection check. They fall into seven families:
Family | Tools | Example question |
Options flow and prices | 10 | “What were the largest SPY options blocks of the session?” |
Exposure | 3 | “How is SPY gamma exposure spread across expirations?” |
Volatility | 4 | “What is NVDA’s IV rank?” |
Open interest and max pain | 6 | “Which SPY strikes hold the most open interest?” |
Stocks and dark pools | 5 | “Which SPY price levels saw the most dark pool trading?” |
News and events | 2 | “Which trading halts were announced in the session?” |
Connection check | 1 | “Is the Quant Data server up?” |
Each data tool matches one REST endpoint in the public API docs.
Can Claude place trades or change my account through Quant Data?
No. Every Quant Data tool reads data and is marked read-only on the server. None places a trade or changes your account.
How much does it cost, and what are the limits?
The Quant Data API is $149.99 a month, or $1,499.99 a year, for every endpoint over REST and MCP. Connecting Claude uses that same subscription.
The request limit is 240 per 60 seconds, plus a burst cap of 20 per second, with no monthly quota. One tool call is one request, and REST and MCP share the limit.
Options data needs a signed market-data subscriber agreement.
Personal use only. Not for external redistribution. Contact us for enterprise pricing.
What are the Quant Data MCP server’s technical details?
The Quant Data MCP Server docs list every tool and the setup for other MCP clients. The server speaks Streamable HTTP and takes the same API key as REST, in an Authorization: Bearer header. Tool arguments sit at the top level of the call (ticker, sessionDate, greekMode), and results are CSV-shaped text, not JSON.
Why connect Claude to Quant Data for options flow?
Quant Data gives Claude consolidated and unconsolidated options flow for 6,000+ tickers, from exchange-licensed data. The same hosted server carries the exposure, open interest and max pain tools.
FAQ
Is there a Claude plugin or connector for options flow data?
Yes. The Quant Data connector in Claude’s directory connects Claude to options flow data. Add it there and sign in with your Quant Data account, which needs an active API subscription.
Is there an MCP server for options flow data?
Yes. Quant Data runs a hosted MCP server for options flow data at https://api.quantdata.us/mcp with 31 read-only tools. There is nothing to install or run.
Can Claude pull gamma exposure (GEX) and max pain over MCP?
Yes. The Quant Data MCP server has three exposure tools (Exposure by Strike, Exposure by Expiration and Interval Map) and two max pain tools (Max Pain and Max Pain Over Time).
Can Claude get stock market data from Quant Data?
Yes. Five Quant Data tools cover stocks: Stock Price Over Time, Equity Prints, Dark Flow, Dark Pool Levels and Market Map. Two more return news articles and exchange notifications.
Do I need an API key to connect Claude to Quant Data?
Not with the Quant Data connector in Claude’s directory: you sign in with your Quant Data account. Not with the Claude Desktop custom connector either, per our API overview. In Claude Code, yes: the config sends your Quant Data API key in an Authorization header.
Do I need to know how to code?
No. With the Quant Data connector in Claude’s directory you add it, sign in and ask in plain English. Claude Code takes one environment variable, one config file and one command.
Where are the full API docs?
Quant Data API overview: API key setup and an overview of the API
API docs: every endpoint
MCP Server docs: every tool and the setup for other MCP clients
Authentication, Rate Limiting and Errors: keys, the request limit and the error codes
I have not signed up for the Quant Data API. How do I?
Click here to see the API plans and get your API key. Click on Learn More if you would like to learn more about what we offer.
Would you like further assistance?
If you have any questions or need further assistance, please don’t hesitate to reach out to the Quant Data team at support@quantdata.us or via our live chat located on the bottom right-hand corner of your screen. We are available on our live chat between 9:30 AM and 5:00 PM (eastern time), Monday through Friday.