XFIV Connect includes an MCP server for MT5 brokers. It lets approved AI assistants read client account data through the Model Context Protocol. Access is read-only by default, the broker sets the scopes, every request is written to an audit log and AI assistants cannot place trades.
MCP, the Model Context Protocol, is an open standard for connecting AI assistants to software. Instead of building a custom integration for every assistant, a system exposes an MCP server. Any compatible assistant can then discover what the server offers and request data in a structured, predictable way.
An MCP server describes a set of tools and resources, such as "read account balance" or "list recent trades". The assistant decides which tool to call to answer a question, the server checks whether that call is allowed, and the result goes back to the assistant as structured data.
For trading, that means a client can ask an assistant "How did my account do this week?" and get an answer built from their real account data, rather than a generic reply. The open question for a broker is who controls that access, and how it is recorded.
XFIV Connect already sits between your MT5 server and the systems around it. Its MCP layer exposes a controlled subset of that data to AI assistants. The assistant never talks to MT5 directly. It talks to XFIV Connect, which applies your rules before anything is returned.
Because the server runs on the broker side, it can cover every account a client holds with you, apply the same scopes across all of them and write every request to the same audit log your team already uses for the API. Your compliance and support teams can see what an assistant asked for and what it received.
With XFIV Connect, your clients can link their trading accounts to AI assistants through the Model Context Protocol. Access is read-only by default, scoped by the broker, and every request is logged for review.
Read the MCP guideAI responses are informational and are not investment advice.
Out of the box, MCP access is read-only. Assistants can read balances, positions and history within their scopes. Order placement is not enabled for AI assistants.
Scopes are set by the broker, not by the assistant. Choose which data areas are available, for which account groups and for which AI clients, and change them at any time.
Each MCP request is written to the audit log with the client, the assistant, the tool called and the time. Your team can review activity, answer client questions and support compliance reviews.
You switch on the MCP layer in XFIV Connect, choose the AI clients you allow and set their scopes.
From the client area, the client links a compatible AI assistant to their accounts and approves the access you allow.
For example, "What is my open exposure on EURUSD?" The assistant picks an MCP tool to answer it.
The request is checked against the broker’s scopes and the client’s own accounts. Anything outside them is refused.
Allowed data goes back to the assistant, and the request is written to the audit log.
The client or the broker can remove access at any time. Later requests are refused.
MetaTrader 5 added MCP support and a native AI assistant in build 6060, released July 23, 2026, with trading permission settings in the terminal. That is a useful tool for individual traders. Broker-side MCP in XFIV Connect solves a different problem: giving a brokerage control over AI access across all its clients.
| Question | XFIV Connect MCP (broker side) | MT5 native AI assistant (terminal side) |
|---|---|---|
| Where it runs | On the broker side, through XFIV Connect | In the trader’s MT5 terminal |
| Who sets permissions | The broker, per AI client and account group | The trader, in the terminal’s settings |
| Accounts covered | All of a client’s accounts with the broker | The accounts open in that terminal |
| Trading | Not available to AI assistants | Controlled by the terminal’s trading permission settings |
| Record of requests | Central audit log the broker can review | See MetaQuotes documentation |
| Best for | Brokers offering AI access to many clients under one policy | Individual traders using AI in their own terminal |
These are the kinds of questions a read-only, scoped MCP connection answers well.
"Summarize my balance, equity and margin across all my accounts."
"Which symbols did I trade most last month, and what was my result on each?"
"What positions do I have open right now, and what is my floating P&L?"
"Explain the swap charges on my statement for last week."
It does not place, modify or close trades. It does not give investment advice; the assistant interprets data, and the broker remains responsible for how the service is offered to clients. It does not let one client read another client’s data, and it does not bypass the scopes you set.
XFIV is a brokerage technology provider, not a broker. Brokers decide whether to offer AI access, to whom, and under which terms, and should take their own legal advice on how that fits their obligations.
A glossary entry on MCP and how trading platforms use it.
Read moreHow the AI agent inside XFIV Portal answers client questions.
Read moreThe MT5 integration API that the MCP layer is part of.
Read moreHow we approach AI and MCP safety, encryption and access control.
Read moreIt is a service that exposes MT5 account data to AI assistants through the Model Context Protocol. In XFIV Connect, it runs on the broker side, is read-only by default and logs every request.
No. Order placement is not enabled for AI assistants. MCP access is for reading data within the scopes the broker sets.
Any assistant that supports MCP can technically connect, but only the AI clients the broker allows are accepted. The broker decides the list.
The MT5 assistant runs in the trader’s terminal with permissions the trader sets. XFIV Connect runs on the broker side, covers all of a client’s accounts and keeps one audit log under broker control. The two can coexist.
Authorized broker staff can review the audit log, which records the client, the assistant, the tool called and the time of each request.
No. MCP gives assistants access to data. XFIV does not provide investment advice, and brokers are responsible for how AI features are offered to their clients.
Book a demo to see the permissions console, the audit log and a client connecting an assistant in the sandbox.
Last reviewed 2026-10-29