Interactive Brokers MCP Server

Interactive Brokers MCP server enabling AI agents to interact with IBKR's brokerage platform — querying account balances and positions, accessing real-time and historical market data, placing and managing orders for stocks, options, futures, and other instruments. Integrates IBKR's Trader Workstation (TWS) or Gateway API into agent-driven trading and portfolio management workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Finance interactive-brokers ibkr trading stocks options mcp-server brokerage finance
⚙ Agent Friendliness
71
/ 100
Can an agent use this?
🔒 Security
83
/ 100
Is it safe for agents?
⚡ Reliability
70
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
70
Error Messages
68
Auth Simplicity
72
Rate Limits
78

🔒 Security

TLS Enforcement
95
Auth Strength
85
Scope Granularity
75
Dep. Hygiene
78
Secret Handling
82

Real money trading — highest risk category. Mandatory human approval for orders. Paper trading for development. TWS credentials extremely sensitive. Comply with SEC/FINRA algorithmic trading rules.

⚡ Reliability

Uptime/SLA
78
Version Stability
68
Breaking Changes
65
Error Recovery
68
AF Security Reliability

Best When

An Interactive Brokers customer wants AI-assisted portfolio management, market data access, or semi-automated trading with human oversight — IBKR's comprehensive market access is invaluable for quantitative workflows.

Avoid When

You need fully autonomous AI trading without human approval gates, use a different broker, or are building HFT systems.

Use Cases

  • Querying account positions and portfolio value from portfolio management agents
  • Accessing real-time market data and quotes from market data agents
  • Placing limit and market orders from algorithmic trading agents
  • Monitoring and managing open orders from trade management agents
  • Pulling historical price data for backtesting from quantitative research agents
  • Executing rebalancing trades based on portfolio drift from automation agents

Not For

  • High-frequency trading (TWS API latency is too high for HFT — use FIX/OUCH protocols)
  • Teams without Interactive Brokers accounts
  • Fully autonomous trading without human oversight — AI trading carries significant financial risk

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: username_password
OAuth: No Scopes: No

IBKR TWS or Gateway must be running locally with API access enabled. Authentication via TWS login. IBKR Client Portal API uses OAuth for web-based access. Paper trading account recommended for development.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

MCP server is free. IBKR accounts require minimum deposits for live trading. Paper trading (simulated) accounts are free for development.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • CRITICAL: Autonomous AI order execution with real money — ALWAYS implement human approval before order submission
  • IBKR TWS must be running and API connections enabled — configure TWS settings before use
  • ALWAYS start with paper trading account — test all order logic thoroughly before live trading
  • IBKR API has 'pace violations' — implement rate limiting (max 50 msg/s) to avoid disconnects
  • Market data subscriptions separate from trading — some data requires paid subscription
  • TWS session timeout (typically 24h) requires periodic re-authentication in long-running agents

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Interactive Brokers MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered