ib-gateway-mcp
Related Servers
Alternatives to ib-gateway-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceAn MCP server that provides an interface for the Interactive Brokers API via the ib_async library. It enables users to manage accounts, access real-time and historical market data, and execute or monitor trades through TWS or IB Gateway.331-
- FlicenseNot gradedqualityCmaintenanceMCP server for Interactive Brokers TWS API, enabling automated financial workflows like portfolio rebalancing through 51+ tools for market data, account management, and order execution, plus real-time WebSocket streaming.-
- FlicenseBqualityDmaintenanceMCP server for Interactive Brokers via IB Gateway, enabling read access to account data and trading capabilities for paper accounts.11-
- AlicenseBqualityCmaintenanceA read-only-by-default MCP server for Interactive Brokers that exposes account, positions, PnL, market data, and trade history from a local TWS/IB Gateway session, with optional trading capabilities.15MIT

Gogi MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants in MCP clients to query real-time market data, inspect portfolio and Web3 wallet balances across brokers, place protected equity/ETF, crypto, forex, options, DeFi swap, and prediction market orders, and run backtests.MIT- AlicenseNot gradedqualityDmaintenanceMCP server for Interactive Brokers that exposes portfolio data, market quotes, trading, and analysis to any MCP-compatible AI client, with support for EU investors and safety-gated trading.1MIT
TDQS
Scored across 50 tools
Every tool targets a distinct resource and action; even the many get_* tools (account_summary vs account_values, positions vs portfolio, historical_bars vs historical_ticks) are carefully separated by purpose and data. Streaming versions (subscribe_*) are clearly differentiated from one-shot snapshots (get_*), so there is no real ambiguity.
All tool names follow a consistent snake_case verb_noun pattern: get_, subscribe_, set_, list_, run_, calculate_, qualify_, search_, and unsubscribe. The verb reflects the access mode and the noun the resource, making the naming scheme predictable and uniform across all 50 tools.
At 50 tools, this is far above the '16-25 feels heavy' range and well into the 'too many' category. While each tool is individually distinct and the breadth of IBKR justifies many of them, several niche or deprecated tools (e.g., get_wsh_metadata, get_depth_exchanges, get_fundamental_data) add bulk and make the surface difficult for an agent to navigate efficiently.
The tool set is heavily tilted toward reading account state, market data, news, and subscriptions, but it completely lacks order placement, modification, and cancellation tools—the core of a trading gateway. get_open_orders even references 'order tools' that do not exist here, so any agent attempting an actual trade workflow will hit a dead end.