Inspect portfolio state
Read net liquidation, cash, margin, buying power, positions, P&L, option legs, Greek coverage, and per-underlying exposure.
IBKR / Interactive Brokers MCP server
Connect IB Gateway or TWS to Claude Desktop, Claude Code, Cursor, Zed, and other MCP hosts. Use account, positions, quotes, official calendars, option chains, scanners, breadth, gamma, and risk-regime data for portfolio analysis and trading-research workflows.
{
"mcpServers": {
"ibkr": {
"command": "/ABSOLUTE/PATH/TO/ibkr",
"args": ["mcp"]
}
}
}
Ask in plain language. The assistant chooses the right MCP tool for portfolio review, market context, risk checks, and trade-plan sizing.
Read net liquidation, cash, margin, buying power, positions, P&L, option legs, Greek coverage, and per-underlying exposure.
Ask for stock or ETF quotes, official open/holiday context, daily bars, option expiries, expected moves, and strike grids from the local IBKR session.
Use configured or ad-hoc IBKR market scanners for movers, losers, unusual volume, gaps, high IV rank, and option volume.
Calculate fixed-fractional share sizing against live NLV, with optional target, R-multiple, and breakeven win-rate math.
Combine volatility, credit, funding, FX carry, dealer gamma, and S&P 500 breadth into a compact risk-regime view.
MCP clients can read and subscribe to stock/ETF quote resources through ibkr://quote/{symbol}.
The boundary is simple: account and market data are available; order entry is not part of the bundled CLI or MCP server.
Use the MCPB for Claude Desktop. Use the shell install for Cursor, Continue, Zed, terminal workflows, or other local MCP hosts.
Download MCPB for Claude Desktop
Open the .mcpb file with Claude Desktop, drag it into Claude Desktop, or install it from Claude Desktop settings. Requires IB Gateway 10.37+ or TWS running locally and an IBKR Pro account with TWS API access.
# Shell, Cursor, Continue, Zed, generic MCP hosts
curl -fsSL https://raw.githubusercontent.com/osauer/ibkr/main/install.sh | sh
ibkr setup claude-desktop
For Cursor, Continue, Zed, or another local MCP host, use an absolute path to the binary. ~ is not expanded by exec.
{
"mcpServers": {
"ibkr": {
"command": "/Users/you/.local/bin/ibkr",
"args": ["mcp"]
}
}
}
These are the kinds of user requests the MCP descriptions are written to route correctly.
Start with Claude Desktop if that is where you plan to ask questions. The other pages cover TWS, Gateway, safety, and deeper portfolio-review context.
Exact setup notes for the short IBKR MCP query.
Use Trader Workstation as the local Interactive Brokers API process.
Use IB Gateway as the lighter local account and market-data bridge.
Install the MCPB and connect Claude Desktop to the local IBKR session.
Compare IBKR MCP servers by local execution, tool coverage, and Claude Code fit.
A prompt-driven review workflow for exposures, options risks, quote freshness, and next checks.
The local MCP surface exposes account and market data, not trading authority.
Brokerage data is sensitive. ibkr keeps the broker connection on the machine already running IB Gateway or TWS and exposes a narrow local read-side interface to the AI host.
Yes. ibkr mcp runs locally as a stdio MCP server and reads account and market data from Interactive Brokers through IB Gateway or TWS.
Claude Desktop, Claude Code, Cursor, Zed, Continue, and other local stdio MCP hosts can launch it.
Not in the standard downloads: the MCP bundle and the plain ibkr tarballs are read-only builds with no place, modify, or cancel order tools compiled in. Each release also publishes a clearly marked ibkr-trading tarball for users who explicitly opt into order management — it ships with warnings and layered safeguards.