Platforms · Software · Providers · Markets
Broker permissions shape agent access
B2BROKER Group has added Model Context Protocol (MCP) connectivity and an AI chat interface to B2TRADER. Traders can link external services including Claude and ChatGPT to their accounts for analysis and, if the broker grants the necessary permissions, trading.
Agents connected through MCP can pull market data and examine portfolio holdings and account history. They can also act on instructions such as closing profitable positions or placing stop-loss orders. Brokers choose between read-only access and full trading permissions, can switch MCP off, and limit each agent to accounts owned by the trader who authorised it.
Other platforms offer different controls
The B2TRADER chat runs through the same MCP connection and can respond to questions about markets, positions and platform functions. A proposed action from this chat needs explicit approval. By contrast, an external agent with full permissions can carry out allowed trades without confirmation for each order.
B2BROKER's embedded AI Assistant arrived earlier this year with forecasts, sentiment indicators, recommendation scores and signals; a later release brought in external statistics and third-party asset news. The company expects the terminal chat to reduce routine first-line support enquiries and says AI connections may help brokers distinguish their platforms. Other models include Leverate's September MCP integration for account analysis and order preparation, with trader confirmation, and CMC Markets' read-only connection for UK CFD accounts.
Freedom24 added AI to Tradernet in August, while ThinkMarkets and cTrader also adopted MCP integrations. A June review from Finance Magnates Intelligence, reported by Finance Magnates, found Claude in nine of the ten integrations it examined.
| Timing or measure | Reported detail |
|---|---|
| Earlier this year | B2BROKER introduced B2TRADER's embedded AI Assistant. |
| September | Leverate launched its MCP connection. |
| August | Freedom24 added AI access to Tradernet. |
| June report | Claude was supported by nine of the ten integrations studied. |
What an operations team should check
The change puts account permissions and order handling at the centre of deployment. Teams should confirm which accounts an authorised agent can reach, how read-only and full access are assigned, and who can disable MCP. They should also establish how agent-initiated orders and position changes appear in existing monitoring and reconciliation processes.
Testing should distinguish the confirmation path for the in-terminal chat from external agents with full access, which can trade without order-by-order approval. Operators should verify how the system handles permitted actions such as modifying or closing trades, and ask what records are available for reviewing those actions. The source does not specify the logging or reconciliation arrangements.
