What Does IBKR's Certified Claude and ChatGPT Connector Actually See, and What Is the Chart Context Gap?

What Is the IBKR Certified MCP Connector?

Interactive Brokers' certified Model Context Protocol (MCP) connector launched with Claude (Anthropic) on June 1, 2026, and on June 22, 2026 IBKR added ChatGPT (OpenAI) and Grok (xAI), with Gemini (Google) still going through certification. It is listed in each platform's connector marketplace as a certified integration. No API keys, no developer account, and no code are required, IBKR clients connect through the standard account authentication flow, and no credentials are shared with the AI provider. This is an enterprise integration built on IBKR's own infrastructure, not a bolt-on API-key connection.

MCP is an open standard that lets AI assistants connect to external data sources and tools. IBKR's implementation follows this standard, meaning any MCP-compatible AI can connect to the same data surface. The certification label indicates IBKR has verified the integration against each platform's requirements.

The connector reads and drafts across IBKR's own market access, more than 170 markets globally, with market and limit orders. Order drafting launched for equities and ETFs on June 1, 2026 and expanded on June 22, 2026 to include options, futures, and futures options. Whatever the AI drafts still executes through IBKR itself; the connector does not route orders anywhere else. For current coverage and the setup guide, see the IBKR Traders' Insight page on connecting Claude and ChatGPT to an IBKR account.

• IBKR press release — June 1, 2026

  Official Interactive Brokers announcement of the certified Claude connector launch.

• IBKR press release — June 22, 2026

  IBKR adds ChatGPT and Grok and extends order drafting to options and futures.

• IBKR Traders' Insight: How to Connect Claude AI and ChatGPT to Your IBKR Account

  Step-by-step connector setup guide from IBKR.

How Do You Connect Claude or ChatGPT to IBKR?

The connection is offered by Interactive Brokers, not by a third party, and you authorise it from inside your own IBKR account rather than by generating an API key and pasting it into someone else's software. That is the main practical difference from the usual broker integration: there is no long-lived secret for you to store, and nothing to rotate if you change your mind.

Once it is authorised, the assistant can read the account data described below and can draft orders for you to review. Drafting is not sending. The order still appears in IBKR for you to approve, and IBKR remains the execution venue.

IBKR maintains the setup steps and the current list of certified assistants on its own site, and those change as new assistants clear certification, so it is worth reading there rather than following a screenshot from an article. What does not change is the shape of the thing: brokerage data flows to the assistant, and your chart does not.

Which Assistants Can Connect, and Where Coding Tools Fit

The certified connector went live with Claude on June 1, 2026 and expanded to ChatGPT and Grok on June 22, 2026, with Gemini still in certification at the time of writing.

Coding assistants sit in a different category and this trips people up. Claude Code, Codex, Cursor and GitHub Copilot all speak the same protocol, but they connect to servers you run yourself rather than to IBKR's certified endpoint. That is a feature rather than a limitation: a local server can expose things IBKR's connector deliberately does not, including the chart you have been drawing on.

If a coding assistant is the tool you actually work in, the practical walkthrough is at Using Codex or Claude Code With IBKR Chart Data, and the build-it-yourself version is at Build a Local IBKR + AI Chart App: The MCP and Connector Pattern.

What Data Does the Connector Expose to Claude and ChatGPT?

The connector gives the AI access to: account summary (balances, net liquidation value, buying power), open positions with cost basis and current values, open orders, margin utilization, trade history, and market data, both real-time quotes and historical price data, across more than 170 markets globally.

Crucially, AI-generated orders do not auto-execute. When Claude or ChatGPT drafts a trade instruction, it routes to a dedicated 'AI Instructions' tab inside the IBKR client interface. The trader reviews and manually submits, and IBKR itself remains the execution venue. This is the compliance architecture: the AI proposes, the human decides, IBKR executes.

The data surface is meaningful. An AI with your positions, open orders, cost basis, current prices, and historical quotes can answer questions about portfolio state, flag concentration risk, and draft structured order instructions for review in the AI Instructions tab.

What the Connector Cannot See: The Chart Context Gap

The connector knows what you own, at what price, and what the market is doing. It does not know why you own it. The chart context, the trendlines drawn before entry, the support zones marked, the indicator confluence that validated the setup, is invisible to the AI through the connector.

This is the chart context gap. The AI can see you are long 500 shares at a certain price with current P&L. It cannot see that your entry was a support-zone retest at a prior structure level, that your exit rule fires if price breaks below a specific level, or that the setup belongs to a pattern you have been tracking across three sessions.

For a technical trader, that missing layer is most of the trade logic. Market data is public. Position data is mechanical. The annotated chart state, the level notes, the drawing geometry, the session tags, is the proprietary context that distinguishes a structured process from a raw account view. For what that context layer looks like when captured explicitly, see How to Make IBKR Chart Work AI-Readable.

Why the Gap Matters in Practice

If you ask Claude 'what should I do with my position?' through the connector, the AI reasons from price, cost basis, and any publicly available information about the instrument. It does not reason from your chart analysis, your analysis is not in the connector's data scope.

That is not a defect in the connector. It is a scope decision: the connector is an account and market data interface, not a charting system. The gap becomes a problem only when traders expect the connector to substitute for chart-context-aware AI workflow. It cannot. The connector answers account questions. Chart questions require chart context.

Traders who want AI to reason about their annotated charts, not just their account, need to export that context explicitly. For how IBKR chart data, levels, and drawing notes can be made AI-readable, see Claude Code IBKR Chart Data Workflow and How to Turn IBKR Chart Notes Into an AI-Readable Trading Journal.

What the Connector Is Genuinely Useful For

The connector is well-suited to portfolio-level account questions: position summaries across symbols, sector concentration review, P&L checks, buying power calculations, and drafting simple equity or ETF orders for review in the AI Instructions tab. For this class of tasks the connector works without supplemental chart context.

The practical limit appears at any question that requires knowing why a position was taken, what the exit conditions are, or whether the current chart setup remains valid. Those questions require chart-context export alongside the connector, not instead of it.

A complete AI-assisted workflow combines the connector for brokerage-side data with a structured chart annotation export for technical context. For a full side-by-side of the two tools, see IBKR's AI Connector vs MyLinedChart: Account Data vs Chart Context. For the architecture of a human-reviewed workflow that combines both layers, see How to Build a Human-Reviewed AI Workflow Around IBKR Charts. For the signals-vs-process question the connector raises, see Can Claude or ChatGPT Give You Trade Signals Through the IBKR MCP Connector?.

IBKR's Connector or a Local Chart Connection: Which Do You Want?

These are not competing products and the choice is not either-or. They answer different questions, and the fastest way to pick is to ask what your question is about.

Reach for IBKR's certified connector when the question is about the account: what you hold, what it is worth, how much buying power is left, what filled yesterday, or drafting a straightforward order for review.

Reach for a local chart connection when the question is about the analysis: where you marked support, which zone a position was taken against, whether the setup you drew last week still holds, or turning a chart you annotated into rules you can reuse.

A trader doing both is the normal case. The two layers stack, and the decision is made per question rather than once. There is a fuller side-by-side at IBKR's AI Connector vs MyLinedChart: Account Data vs Chart Context, and the build-versus-chat framing at Codex and Claude Code vs the IBKR Connector: Building Workflows vs Chatting With Your Account.

Which Other Brokers Can You Connect to Claude or ChatGPT?

IBKR is the broker with its own certified connector, which is why it comes up first. It is not the only account you can put in front of an assistant, but the route is different: instead of the broker certifying an assistant, you run a local connection and point it at whichever broker or market-data account you already pay for, using your own keys.

That covers brokers including Schwab and Alpaca alongside IBKR, market-data services such as Alpha Vantage, Finnhub and Twelve Data, and the crypto venues that publish data openly and need no key at all. The current list lives at Data provider fit rather than in an article, because it moves.

Two things stay true across all of them. Your credentials stay on your device rather than passing through anyone else's servers, and the connection is read-only: it reads your chart and marks it up, and it never sends an order.

For the crypto venues that need no account or key, see Crypto Charts With No API Key: Binance, Coinbase, Kraken.

Closing the Gap: an MCP That Sees, and Now Draws On, the Chart

MyLinedChart ships its own local direct connection that starts exactly where IBKR's certified connector stops: it reads the chart context the connector cannot see, drawings, levels, indicator state, session notes, from the app running on your own device.

That MCP server now goes one step further than reading. Its propose_chart_changes tool lets the AI draw a level, add or reconfigure an indicator, or set the chart's symbol/timeframe/view, closing the chart context gap from the other direction, by helping maintain the very chart state the IBKR connector can't reach.

The compliance shape should look familiar: IBKR's connector routes every AI-drafted order to an 'AI Instructions' tab for the trader to review and manually submit before anything executes. MyLinedChart's chart-write channel uses the same pattern, every proposed drawing, indicator, or view change is confirmation-gated (or auto-applied only if you've explicitly marked a source 'always allow'), and AI-made items are tagged separately from your own so they're never silently mixed in.

The scope stays deliberately narrow on both sides. IBKR's connector can draft an order but never executes it without you. MyLinedChart's MCP can draw on your chart but can never place, modify, or cancel a trade, account and order access remain fully read-only. Two different tools, the same underlying rule: the AI proposes, you decide. See https://mylinedchart.com/mcp for the full tool list.

Can I connect ChatGPT to Interactive Brokers?

Yes. IBKR runs a certified connector that ChatGPT, Claude and Grok can use, authorised from inside your IBKR account rather than by sharing an API key. It reads account data and can draft orders for you to approve, and IBKR remains the execution venue. It does not read your chart.

Which brokers can I connect to Claude or ChatGPT?

IBKR is the one with its own certified connector. For other accounts, including Schwab and Alpaca and market-data services like Alpha Vantage, Finnhub and Twelve Data, you run a local connection with your own keys instead. Your credentials stay on your device and the connection is read-only.

What does IBKR's certified connector give Claude and ChatGPT access to?

Account balances, open positions with cost basis, margin status, trade history, and market data including real-time and historical quotes across 170+ global markets. Order drafting launched for equities and ETFs in June 2026 and expanded on June 22, 2026 to include options and futures.

Does the IBKR connector include chart drawings or technical indicator state?

No. The connector exposes account and market data only. Chart drawings, annotated support and resistance levels, marked zones, indicator values, and session review notes are outside the connector's data scope.

Can Claude or ChatGPT execute trades automatically through the IBKR connector?

No. AI-generated trade instructions go to an 'AI Instructions' review tab in the IBKR client interface. The trader must review and manually submit. Nothing executes without explicit client action.

What is the chart context gap with the IBKR connector?

The gap is the difference between what the AI can see through the connector, account state and market prices, and what it cannot see, chart drawings, annotated levels, TA indicator state, and setup notes. Most of the reasoning behind a technical trade lives in chart context, not account data.

Is there a tool that closes the chart context gap?

MyLinedChart's own local direct connection reads the chart context the IBKR connector cannot see, and its propose_chart_changes tool can also draw levels, configure indicators, and set the view, every change confirmation-gated, same as IBKR's own AI Instructions review step for orders. It stays read-only to your account and orders: it can never place, modify, or cancel a trade.

How many markets does the IBKR connector cover, and where do orders execute?

The connector reads and drafts across more than 170 global markets. Whatever Claude or ChatGPT drafts is submitted through the AI Instructions tab for the trader's manual approval, and IBKR itself remains the execution venue, orders never route anywhere else.