MT5 Build 6060: MCP, AI agents, and new account roles

MetaQuotes shipped MetaTrader 5 build 6060 on 23 July 2026, and it is not a routine maintenance build. The terminal now speaks the Model Context Protocol natively, accounts get two new permission levels beyond the master/investor split, and passwords can be replaced with passkeys. There is also a long list of MQL5 additions that matter if you write indicators or EAs.

Here is what changed, and what it actually means depending on what you build.

The headline: native MCP and an AI assistant in the terminal

Build 6060 adds built-in support for the Model Context Protocol — the standard AI assistants use to talk to external tools. In practice:

• AI agents can access market data and trading functionality directly from the terminal.
• External model providers are supported out of the box: OpenAI, Anthropic, Gemini, DeepSeek, and Ollama (so a local model works too).
• Signing in grants a free MQL5 Lite plan automatically.
• AI settings synchronize between the terminal and MetaEditor.

The assistant itself can analyze market conditions, open positions, and trading history, and explain instruments and market events. MetaQuotes clearly thought about the failure modes: there are security settings governing whether the AI may initiate trading operations at all, and controlled access to network requests and command-line operations. Those defaults deserve a careful read before you let any model near a live account.

Terminal MCP is for traders. It is not an application API.

This is the distinction worth being precise about. Build 6060 puts an AI in your terminal — one machine, one running MetaTrader instance, alive only while the terminal is. That is genuinely useful for a trader at a desk asking "what is my exposure on gold right now?"

It does not change the picture for anyone building a product. A portfolio tracker, a copier service, or a prop-firm dashboard cannot sit on top of a desktop terminal's MCP session — you still need server-side infrastructure: accounts that stay connected without a desktop open, an API your backend can call, webhooks that fire whether or not anyone is logged in.

The direction of travel, though, is the same one we have been building for: AI agents are becoming first-class consumers of trading systems. It is why MetaKit publishes an llms.txt — the complete public API written for coding agents, so an AI assistant integrating MetaKit into your app has every endpoint, error code, and payload shape without guessing.

New account access levels — read this if you run a prop firm or copier

Until now MT5 effectively had two credentials per account: the master password (full control) and the investor password (read-only). Build 6060 adds two more modes, each with its own password:

This is a meaningful change to the credential model. Handing a third party trading access used to mean handing over the master password — and with it the ability to change that password and lock you out, or touch funds through the broker's tooling. A Trader-mode password bounds the damage: trades only, no credential changes, no money movement.

For prop firms evaluating traders, copier services collecting follower credentials, and account-management setups splitting execution from treasury, this is the feature in the release. Note it requires broker-side support, so availability will vary broker to broker.

Passkeys replace passwords (optionally)

Accounts can now authenticate with passkeys instead of passwords — stored either on a phone (paired via QR code and Bluetooth) or on a FIDO2 hardware key. It is phishing-resistant in a way passwords never were, which matters in a space where credential theft is the standard attack.

Enablement is broker-side and optional; password login remains. There is a Passkey Manager for removing or resetting registered keys.

MQL5 additions worth knowing

A few of these have been on wishlists for years:

• SymbolInfoCommissions — a new function returning commission information for a symbol, including the tiers array. Commission structures have historically been opaque to programs; analytics that previously had to infer costs from deal history can now ask directly.
• TextOut is up to three times faster — significant if you render custom panels or draw on charts every tick.
• WebRequest timeout handling fixed — anyone calling external APIs from an EA has probably fought this one.
• CHARTEVENT_CHART_CHANGE now fires when CHART_PRICE_MIN/MAX change.
• MQL_LAST_OPENBLAS_ERROR — failed OpenBLAS calls now expose their info parameter instead of failing opaquely.

For quant work, the matrix library grew substantially: structural analysis via MatrixInfo, matrix/vector serialization (Write/Read, binary and CSV variants), five new orthogonal factorization methods backed by LAPACK, a Sylvester equation solver, constrained least squares (LeastSquaresGaussMarkov2), and mixed real/complex BLAS level-3 multiplication. The t-distribution quantile calculation was also corrected — worth re-running anything that depended on it.

MetaEditor picked up code folding, occurrence highlighting for selected identifiers, and a switch to UTF-8 (without BOM) for .mq5/.mqh files.

One removal: FTP report publishing is gone

Build 6060 removes the terminal's FTP support for publishing trading reports. If some downstream process still ingests those FTP drops, it stops working when the terminal updates. The durable replacement is pulling data over an API or receiving webhooks on trade events rather than parsing exported reports — which is, candidly, the architecture those pipelines should have had anyway.

Smaller fixes worth a line: the empty trading dialog for Instant Execution symbols above the Request Execution volume threshold is resolved, Regression Channel calculations are corrected (including ObjectGetValueByTime for regression and std-dev channel objects), custom spreads now apply correctly in "Open prices only" testing, and percentage-based swap calculations in the tester are fixed.

If you use MetaKit, what changes?

Nothing on your side. MetaKit runs an isolated terminal per connected account and manages terminal builds as part of the platform — the API surface you integrate against does not change when MetaQuotes ships a new build. Your accounts, equity monitors, copiers, and webhooks carry on.

The two items worth acting on:

1. Trader-mode passwords (once your broker supports them) are a better credential to connect with than a master password when you only need execution — the same reasoning as our long-standing advice to use investor passwords for read-only accounts.
2. If anything you run still consumes FTP-published reports, migrate it to API pulls or webhooks before the build reaches that terminal.

The full release notes are on metatrader5.com.