Account-Scoped Access
A connected agent operates only on the accounts of the trader who approved it.
Essentials for Brokers
Traders can point Claude, ChatGPT, or an agent they built in house at a B2TRADER account through MCP, and ask it to read market data, portfolio, history, and analytics or, with full access, to trade.

Broker controls
A connected agent operates only on the accounts of the trader who approved it.
Each deployment can turn MCP off, keep it read-only, or allow full trading access.
The agent connects through the platform sign-in. Full access asks for an explicit trade-scope consent.
Two surfaces
Read-only is for analysis, such as a portfolio summary. Full access is for actions the trader has approved. The broker chooses off, read-only, or full access for the deployment. Trades inside the terminal still go through AI Chat, which asks for confirmation.
Market data, portfolio, history, and analytics. A trader can ask for a portfolio summary. Tools that place or change orders are not on this surface.
Everything in read-only, plus placing, cancelling, and closing orders and setting price triggers. A trader can ask the agent to close positions that are in profit, or to set a stop-loss on every open position. There is no per-trade confirmation inside the external agent.
MCP clients that support the platform sign-in flow, including Claude, ChatGPT, and compatible clients a broker builds in house.
No. The read-only surface does not expose tools that place or modify trades.
No. After the trader approves full access, the agent can perform supported trading actions without a confirmation on every order. AI Chat inside the terminal confirms its own trades separately.
Yes. MCP can be disabled, limited to read-only, or opened to full access for a deployment.
Book a walkthrough and choose the access mode for your deployment.