ibkr - IBKR MCP server for TWS and IB Gateway
MCP tools · MCP resources · Configuration · Architecture · Platform settings · Agentic use · Mobile app
Agentic portfolio analysis and trading-research workflows for IBKR MCP, TWS, and IB Gateway.
ibkr turns your local IB Gateway or TWS session into structured account and market context for the terminal, Claude Desktop, Claude Code, Cursor, Continue, Zed, and other MCP hosts. It is the local ibkr mcp TWS bridge for portfolio review, exposure mapping, options diagnostics, market-regime checks, scanner-driven research, watchlist monitoring, and position-sizing math.
For MCP users, ibkr mcp is a local IBKR workflow layer for semi-professional retail traders who want agentic portfolio and trading-research analysis on live broker data. The bundled MCP surface is deliberately no-broker-write: it can analyze and size plans, and it can draft preview-only stock/ETF LMT orders, but it cannot place, modify, cancel, or transmit broker orders.
Use it from a shell:
ibkr status
ibkr positions --by underlying
ibkr regime
ibkr canary
ibkr market-events --symbol GME --json
ibkr watch IBM --add
ibkr watch
ibkr calendar --market us --date 2026-05-25
ibkr quote SPY --watch
ibkr size --symbol AAPL --entry 207.50 --stop 202.50 --risk-pct 1
ibkr settings show
Or connect it to Claude Desktop, Claude Code, Cursor, Continue, Zed, or any MCP host and ask:
"What's in my IBKR account?"
"Review my portfolio and rank the risks I should look at today."
"Show my AAPL exposure, including option deltas."
"How does the market regime look today?"
"Should I hold, watch, de-lever, or liquidate risk?"
"Is Xetra open on Whit Monday?"
"If I buy 100 MSFT at 418 with a stop at 408, what's my EUR risk?"
Your account data stays on the machine running IB Gateway or TWS unless you choose to send it to an MCP host. The project ships as one Go binary with a CLI, a local MCP server, and a Go library. No Python runtime, Java runtime, or hosted service is required.
Contents — Install · What you get · Pick your path · How it works · Configure · Safety · Other install paths · Troubleshooting
Install
Prerequisites. A running IB Gateway 10.37+ or TWS (paper or live) on the same machine. Auto-discovered on the four standard ports. An IBKR Pro account (IBKR Lite cannot use the TWS API).
Claude Desktop
Download the latest MCP Bundle:
https://github.com/osauer/ibkr/releases/latest/download/ibkr.mcpb
Open the .mcpb file with Claude Desktop, drag it into Claude Desktop, or use Settings -> Extensions -> Advanced settings -> Install Extension. Quit Claude completely and relaunch it after installation.
The MCPB bundles the ibkr binary for macOS and Linux, runs it locally through stdio, and does not require a separate shell install. Windows Claude Desktop is not supported because ibkr has no native Windows daemon; WSL works through the shell install path below.
Shell, Cursor, Continue, Zed, and generic MCP hosts
curl -fsSL https://raw.githubusercontent.com/osauer/ibkr/main/install.sh | sh
ibkr setup claude-desktop
The installer downloads the release for your OS and architecture, verifies the checksum, installs ibkr in ~/.local/bin, and adds that directory to your shell rc when needed. On macOS, it also clears Gatekeeper quarantine.
ibkr setup claude-desktop writes the legacy MCP server entry to Claude Desktop. Prefer the MCPB path above for Claude Desktop unless you specifically want one shared shell-managed binary. Skip the setup command if you only want the shell tool.
For v1.0.0+ releases, the installer, ibkr update, and the MCPB release asset are covered by the signed SHA256SUMS file. The MCP Registry metadata also carries the MCPB file SHA-256. Other install paths.
What you get
