Schema | Interactive Brokers MCP Server

Interactive Brokers MCP Server

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`IB_USERNAME`	No	Your Interactive Brokers username (required when IB_HEADLESS_MODE is true)
`IB_HEADLESS_MODE`	No	Enable headless mode for automated environments or when you prefer not to use a browser for authentication	false
`IB_PASSWORD_AUTH`	No	Your Interactive Brokers password (required when IB_HEADLESS_MODE is true)

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

Capability	Details
`tools`	{ "listChanged": true }

Tools

Functions exposed to the LLM to take actions

Name	Description
authenticateA	Authenticate with Interactive Brokers. Usage: `{ "confirm": true }`.
get_account_infoB	Get account information and balances. Usage: `{ "confirm": true }`.
get_positionsC	Get current positions. Usage: `{}` or `{ "accountId": "<id>" }`.
get_option_chainA	Get option expirations and strikes for an underlying symbol. Usage: `{ "symbol": "AAPL" }` or `{ "symbol": "AAPL", "exchange": "SMART" }`.
resolve_option_conidA	Resolve a specific option contract conid. Usage: `{ "symbol": "AAPL", "expiry": "JAN27", "strike": 200, "right": "C" }` or add `{ "exchange": "SMART" }`.
get_market_dataA	Get real-time market data. Usage: `{ "symbol": "AAPL" }` or `{ "symbol": "AAPL", "exchange": "NASDAQ" }`.
place_orderA	Place a trading order. Examples: Market buy: `{ "accountId":"abc","symbol":"AAPL","action":"BUY","orderType":"MKT","quantity":1 }` Limit sell: `{ "accountId":"abc","symbol":"AAPL","action":"SELL","orderType":"LMT","quantity":1,"price":185.5 }` Stop sell: `{ "accountId":"abc","symbol":"AAPL","action":"SELL","orderType":"STP","quantity":1,"stopPrice":180 }` Option buy: `{ "accountId":"abc","symbol":"AAPL","secType":"OPT","expiry":"JAN27","strike":200,"right":"C","action":"BUY","orderType":"LMT","quantity":1,"price":4.5 }` Option by conid: `{ "accountId":"abc","conid":123456789,"secType":"OPT","action":"BUY","orderType":"MKT","quantity":1 }` Suppress confirmations: `{ "accountId":"abc","symbol":"AAPL","action":"BUY","orderType":"MKT","quantity":1,"suppressConfirmations":true }`
get_order_statusA	Get the status of a specific order. Usage: `{ "orderId": "12345" }`.
get_live_ordersA	Get all live/open orders for monitoring and validation. Usage: `{}` for all accounts or `{ "accountId": "<id>" }` for a specific account. This is the recommended way to validate that market orders were executed successfully after placing them.
confirm_orderB	Manually confirm an order that requires confirmation. Usage: `{ "replyId": "742a95a7-55f6-4d67-861b-2fd3e2b61e3c", "messageIds": ["o10151", "o10153"] }`.
get_alertsC	Get all trading alerts for an account. Usage: `{ "accountId": "<id>" }`.
create_alertC	Create a new trading alert. Usage: `{ "accountId": "<id>", "alertRequest": { "alertName": "Price Alert", "conditions": [{ "conidex": "265598", "type": "price", "operator": ">", "triggerMethod": "last", "value": "150" }] } }`.
activate_alertA	Activate a previously created alert. Usage: `{ "accountId": "<id>", "alertId": "<alertId>" }`.
delete_alertC	Delete an alert. Usage: `{ "accountId": "<id>", "alertId": "<alertId>" }`.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored 2026-09-10 01:05 across 14 tools

Disambiguation4/5

Most tools have distinct purposes (alerts vs orders vs account data), but get_live_orders and get_order_status could be confused since both relate to order monitoring. get_alerts vs create/activate/delete_alert are clear, and get_option_chain vs resolve_option_conid are related but distinct enough.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (get_, create_, activate_, delete_, place_, confirm_). Minor deviation: 'authenticate' lacks a noun object, and 'resolve_option_conid' is slightly more verbose than the others, but overall the pattern is predictable.

Tool Count5/5

14 tools is well-scoped for a trading platform server covering authentication, account info, market data, orders, and alerts. Each tool addresses a distinct workflow need without excessive overlap or bloat.

Completeness4/5

The server covers core trading workflows: authentication, account/position queries, market data, order placement/status/confirmation, and alert lifecycle (create, activate, delete, list). Missing order cancellation/modification and position closing are notable gaps, but the primary use cases are covered.

Maintenance

ActivityStale

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers