Platforms · Software · Providers · Markets
PrimeXBT opened its client accounts to ChatGPT and Claude through the Model Context Protocol (MCP) on 4 November 2026. The broker's assistants can prepare orders, but the client must approve each one before it is sent. B2Broker added MCP access to its B2TRADER platform last week, with brokers deciding how much authority an agent receives.
PrimeXBT serves CFD and crypto futures traders. Its assistant can prepare orders at market, limit prices or stop levels.
Before approval, clients see the estimated liquidation level, with use, margin, fees and price also included in the preview, the broker said. On B2TRADER, brokers can disable MCP, permit read-only access or allow agents to submit, amend and exit trades.
How order approval is configured
The two platforms place the confirmation decision in different hands. PrimeXBT requires the client to approve every order.
With B2TRADER, an agent granted full access can act without a separate confirmation for each trade. B2Broker said that orders put forward by B2TRADER's own AI Chat still need the client to confirm them.
Other providers use different safeguards. Leverate's MCP for Traders presents order size, price, stops and the effect on margin before seeking approval. Capital.com's server, offered to Middle East and North Africa clients, displays a trade preview and requires two confirmation steps. Claude on Interactive Brokers prepares an instruction for the client to convert into an order. Axi clients can mark an action as always allowed, removing Claude's further confirmation prompts for that action.
PrimeXBT's preview includes an estimated liquidation level, a detail not present in the earlier launches covered by Finance Magnates. That level can move as the market price changes in a leveraged crypto position.
Which platforms and accounts are included
PrimeXBT clients connect an assistant with a link and their broker login, then choose Read-only or Read & Trade. The integration is available for demo and live accounts on PXTrader 2.0. PrimeXBT said answers on charges, account margin needs and platform rules draw on live account information and its knowledge base. MCP does not enable withdrawals or fund transfers.
Jonatan Randin, senior market analyst at PrimeXBT, said the integration brings trading data and functions into AI assistants that clients already use. The broker has also introduced a Trading API for algorithmic and quantitative traders to connect their own bots and dashboards. It supports order and position handling, requires two-factor authentication and can use IP restrictions.
Like the MCP, it cannot transfer money. ThinkMarkets also kept fund movement outside its AI order-execution feature on ThinkTrader, introduced in June.
Finance Magnates' reporting found at least six brokers and trading-technology firms had enabled AI assistants within client accounts since June. Interactive Brokers expanded its connector to work with almost any MCP-based tool in July. PrimeXBT's product range grew by 101 coins in September 2025.
For B2Broker, access controls are set by each broker, and an agent sees only accounts belonging to the trader who authorised it. Arthur Azizov, founder and CEO of B2Broker, said the addition raises the question of who controls an assistant's permissions. B2Broker is promoting read-only access through AI marketplaces and expects its in-terminal chat to reduce routine support requests. The MCP layer is the third part of its B2TRADER AI programme, following an assistant added in April with forecasts, sentiment indicators and trading signals, according to the company.
What this changes for operators
For a PrimeXBT client or broker integrating an assistant, the immediate control point is order approval: every prepared order needs a client decision, and the preview contains price and risk fields. Operators should check how Read-only and Read & Trade map to account permissions, and confirm how the displayed estimate is refreshed before approval. The source does not specify the timing or update behaviour.
B2TRADER puts more of the permission model in the broker's hands. Firms considering agent access should establish which accounts an agent can see, which actions its selected level permits, and how those permissions are changed or audited. The source does not detail integration work, logging, service costs or operational procedures, so those points need to be confirmed with the provider before deployment.
