Skip to main content
Glama
selvakumarEsra

ibkr-mcp-server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IBKR_READONLYNoSet to '1' to disable all order tools (read-only mode).0
IBKR_AUDIT_LOGNoFile path for audit log of order operations.~/.ibkr-mcp-server/audit.log
IBKR_CLIENT_IDNoClient ID for TWS/IB Gateway connection.17
IBKR_TRADING_MODENoTrading mode: 'paper' or 'live'. Live trading requires explicit opt-in.paper

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
statusA

Return connection state, trading mode, and gateway info.

get_account_summaryD

Cash, net liquidation, buying power, margin.

get_positionsC

Open positions with market price enrichment.

get_pnlC

Account-level or per-position P&L.

get_executionsC

Today's fills (or since ISO timestamp).

search_symbolC

Search IBKR for symbols matching a query.

qualify_contractC

Resolve a symbol to a canonical contract with conid.

get_quoteC

Snapshot bid/ask/last/volume.

get_historical_barsD

Historical OHLCV bars.

place_orderC

Place a single-leg market/limit/stop/stop-limit order.

place_bracket_orderC

Place a bracket: entry + take-profit + stop-loss.

modify_orderC

Modify an existing open order.

cancel_orderC

Cancel an existing open order.

list_open_ordersC

List currently open orders.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct operation: order management (place, modify, cancel, list, bracket), data retrieval (account, positions, P&L, quotes, executions, historical bars), contract resolution (qualify, search), and connection status. No significant overlap.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case (e.g., get_quote, place_order, list_open_orders). Naming is predictable and readable.

Tool Count5/5

With 14 tools, the server is well-scoped for a trading API, covering orders, account info, market data, and contract resolution without being overloaded or sparse.

Completeness4/5

Core trading workflows are well-covered: full order lifecycle, account and position monitoring, market data, and contract lookup. Minor gaps like advanced order types or market depth are absent, but the essential surface is complete.

Maintenance

ActivityInactive
ResponsivenessNo issues