Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Read IBKR positions, balances, P&L, orders and market data, and draft trades you approve in IBKR.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Interactive Brokers MCP server connects a live IBKR brokerage account to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 10 tools reading positions, balances, P&L, orders, trades and market data. The agent can also draft trade instructions, which IBKR queues inside its own platforms for you to approve or reject.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
get_order_instructions is unresolved. No source we found establishes whether it reads the pending instruction queue or creates an entry in it./v1/api/mcp-public for manually added clients across three of its own pages; Anthropic's directory publishes /v1/api/mcp, which no IBKR document we found mentions. Both authenticate. We could not compare their tool surfaces.get_price_snapshot or get_price_history requires, or whether unsubscribed users receive delayed quotes. Treat any price the agent reports as needing its own timestamp.llms.txt addresses AI models directly. It contains a "Prohibited Interpretations" block instructing "the model" what it "must not" say about IBKR's account-opening requirements. That is publisher guidance for answer engines, not documentation about this connector, and we treated it as data rather than as instructions. Readers auditing agent behaviour should know the file exists.No tool submits an order to the market. IBKR states plainly that instructions never become orders automatically, and that every instruction must be reviewed and explicitly confirmed inside an IBKR application before any action is taken. A drafted instruction lands in an AI Instructions tab in Client Portal, IBKR Desktop, Mobile, GlobalTrader or Trader Workstation, where you press Review and Submit, or Reject.
Two application scopes, mcp.read and mcp.write, plus identity claims. IBKR's RFC 9728 resource descriptor declared both on 2026-08-22, and its authorization server advertises openid, profile, email, account-ids, mcp.read and mcp.write. Unlike most connectors in this catalogue, a read and a write permission genuinely exist as separate grants here, so the boundary is not purely cosmetic.
Nothing in the listed surface does. All 10 tool names Anthropic publishes begin with get or search, none references a transfer, withdrawal, deposit or bank instruction, and IBKR's documentation describes the integration only as portfolio analysis plus reviewable trade instructions. IBKR does run funding endpoints in its separate Web API, but that is a different surface this connector does not name.
No. IBKR's developer documentation covering Web API, TWS API, FIX and Excel contains no MCP section at all, and neither its AI Integration marketing pages nor its platform user guides name a single tool. The 10 names come from Anthropic's directory, so there is no second list to diff against and no clean-listing claim is available.
Because a write exists that the 10 listed names do not account for. Nine begin get and one begins search, yet the server declares an mcp.write scope and IBKR's own example prompts create instructions. The likeliest explanation is that the directory lists a subset and the instruction-creating tool is unlisted, so read the clean listing as incomplete rather than as proof nothing writes.
Anthropic's directory lists only the first, while IBKR's own pages tell any other MCP client to use the second. Both returned an authentication challenge on 2026-08-22 and both publish an RFC 9728 descriptor naming the same two scopes and the same authorization server. Whether their tool surfaces are identical could not be established without signing in.
IBKR says explicitly that it does not. Its disclosures state that information generated through the AI integration is not investment advice or a recommendation from Interactive Brokers, that IBKR does not guarantee its accuracy or completeness, and that you are responsible for independently verifying it. IBKR also warns that a drafted instruction may not be accurate or reflect what you wish to do.
Through Manage Third-Party Consents in Client Portal. IBKR's user guides direct you to the profile icon in the top right corner, then Settings, then Manage Third-Party Consents, then Revoke Access. The same guides note that connecting requires reading and signing a set of agreements and disclosures, and selecting which account to grant access to where you hold several.
mcp-public endpoint, the example prompts and the IN/JP restriction. · retrieved 2026-08-22mcp-public connector URL, the single-account authorisation and the "In this release" qualifier. · retrieved 2026-08-22llms.txt — and the Web API section index at (retrieved 2026-08-22). Checked for MCP content; there is none. · retrieved 2026-08-22llms.txt (retrieved 2026-08-22) · retrieved 2026-08-22https://api.ibkr.com/v1/api/mcp and https://api.ibkr.com/v1/api/mcp-public, RFC 9728 descriptors at .well-known/oauth-protected-resource under each, and authorization server metadata at https://api.ibkr.com/.well-known/oauth-authorization-server (2026-08-22) · retrieved 2026-08-22robots.txt at permits every path used here and carries no Content-Signal line.Connect Interactive Brokers (IBKR) once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.