PrimeXM XCore Integration for MT4 and MT5 Brokers

What is PrimeXM XCore?

PrimeXM XCore is a hosted trading and liquidity aggregation engine that sits between a broker's trading platforms and its liquidity providers (LPs). PrimeXM describes it as follows:

"PrimeXM's XCore is the industry leading solution for those seeking an ultra-low latency order management, risk and reporting solution."— PrimeXM, XCore page (accessed October 2026)

According to the same page, XCore aggregates multi-asset liquidity "across an excess of 120 industry leading market makers" and supports MT4/MT5, FIX API and PrimeXM's own web trading interface. PrimeXM's home page uses newer, larger numbers: "A community of over 300 financial partners" and "170 Liquidity Providers". Both pages were live when we checked, so cite the figure with its page.

PrimeXM states that it was established in 2010 and that its infrastructure hubs are the Equinix data centres LD4 (London), NY4 (New York), TY3 (Tokyo) and SG1 (Singapore). It is not a client-facing platform but the execution and risk layer behind your MetaTrader server.

FXSUPPORT is an independent MT4/MT5 support company, not affiliated with PrimeXM or MetaQuotes. XCore is one of the technologies we work with, alongside oneZero Hub, Match-Trade and FIX API connections.

How the MT4 Bridge and MT5 Gateway connect to XCore

MetaTrader connects to XCore through a plugin that PrimeXM installs on the MetaTrader server side. On MT4 it is the MT4 Bridge and on MT5 it is the MT5 Gateway. PrimeXM describes them this way:

"PrimeXM's MT4 Bridge and MT5 Gateway is a powerful yet light-weight server side plugin which connects MT4 and MT5 platforms to the client's XCore order management and reporting engine."— PrimeXM, XCore Solutions (accessed October 2026)

PrimeXM lists these bridge features: full support for parallel processing, "thousands of trades per second", synchronisation between MetaTrader and XCore, complex order routing, and partial fill and sweep-the-book handling. It adds that execution rules can be fine-tuned per MT account, symbol and order type "without the need of server restart".

 Clients (MT4/MT5 terminals, WebTrader, mobile)
                 |
        MT4 / MT5 trade server
                 |  PrimeXM MT4 Bridge / MT5 Gateway (server-side plugin)
                 v
        XCore (dedicated instance, Equinix LD4 / NY4 / TY3 / SG1)
        - aggregation, markups, routing
        - A-book / B-book / custom risk models
        - monitoring, reporting, MT Analytics
                 |  FIX sessions (cross-connects or internet)
                 v
   LP 1      LP 2      LP 3 ...      Post-trade / give-up

MT5 Gateway: what changed when it launched

MetaQuotes published PrimeXM's MT5 Gateway release on 22 May 2017. The announcement said the gateway "takes into account all new features of the MetaTrader 5 platform, including support of the Market Depth". It also said the MetaTrader 4 Gateway to PrimeXM was "used by 200 brokers around the world" at that time, which is a 2017 figure. Finance Magnates quoted PrimeXM as saying that it had tested the MT5 integration with customers since November 2016.

Coverage accounts and margin accounts

PrimeXM's MT4/MT5 page lists coverage functionality: accounts set up inside MetaTrader that record trades executed in XCore, for monitoring and exposure tracking. In August 2020 FX News Group reported that PrimeXM had added automatic synchronisation between XCore Margin accounts and MT4 Coverage accounts. Margin accounts handle pre-trade credit checks, so if you serve B2B or FIX API clients, decide early whether risk is checked before the trade (margin accounts) or after it (coverage accounts).

MT4 versus MT5 on the MetaTrader side

MetaQuotes states that "The MetaTrader 4 trading platform licenses are no longer available for purchase." New projects therefore start on MT5, which differs in ways that affect the bridge: netting and hedging accounts (MT4: hedging only), unlimited symbols (MT4: 1,024) and 6 pending order types (MT4: 4). Each changes symbol mapping and the test plan. If you are moving platforms at the same time, see our MT4 to MT5 migration service.

PrimeXM XCore integration with MT4/MT5: step by step

A clean XCore integration has nine stages, from scoping to post-launch tuning. This is the sequence FXSUPPORT follows. PrimeXM handles provisioning and its own infrastructure; the split of other tasks depends on your contract with PrimeXM.

1. Scope and inventory. List every MT4/MT5 server, client group, symbol (with suffixes), LP, execution model and any FIX or B2B taker. Record current routing, markups and swap sources.
2. Hosting and network decision. Choose where the MetaTrader server runs relative to XCore. PrimeXM's hosting page says clients can host "MT4/MT5 servers and XCORE suites" in its Equinix NY4, LD4, TY3 and SG1 suites. The alternative is your own servers connected over the internet or a private line. We support both, including our own server hosting in the UK and the Netherlands.
3. XCore instance and accounts. PrimeXM provisions the dedicated instance. Then set up users, portal permissions, and Margin, NOP or Risk accounts according to your risk model.
4. LP connectivity. Request FIX sessions from each LP, exchange session details, and bring up pricing and trading sessions. Check symbol lists, contract sizes, volumes and trading hours against each LP's specification.
5. Bridge or gateway installation. Install the PrimeXM MT4 Bridge or MT5 Gateway on the trade server, then check it in a maintenance window before enabling any live group. Configure the feeder for quotes and the trading connection for orders.
6. Symbol mapping and aggregation. Map MetaTrader symbols, including suffixed variants, to XCore instruments. Build liquidity pools per symbol and time frame, and define markup profiles. Synthetic symbols and baskets can also be configured in XCore.
7. Routing and risk rules. Assign A-book, B-book or custom models per group and symbol. Set exposure limits per symbol, currency and time frame, overflow rules to LPs, and news-time restrictions. Check MT5 netting/hedging mode.
8. Testing in demo and UAT. Run the test plan below on a demo MT server or demo groups connected to XCore, then repeat a reduced set on live with small internal accounts.
9. Go-live and tuning. Move groups in stages, watch rejections, slippage and latency, and tune routing and markups from live data. Agree alert recipients and daily reports.

Timing depends mostly on LP onboarding and PrimeXM provisioning, not the MetaTrader work.

Monitoring XCore after go-live

After launch, the work shifts from configuration to monitoring execution quality, connectivity and reconciliation every trading day. XCore already provides the tools, and PrimeXM lists "Custom automated email alerts to notify your team when there might be a problem", connector and LP status in real time, and historic log access. What brokers usually lack is someone watching them.

FXSUPPORT's MetaTrader support covers 24/5 monitoring of these points, end-of-day risk reports, toxic-flow lists, session and DST/holiday schedule checks, and log monitoring, with a 99.9% uptime target for the infrastructure we manage. Risk operations are described on our forex risk management page.

XCore compared with other bridge options

XCore is one of several ways to connect MetaTrader to liquidity; the choice depends on volume, risk model and how much you run yourself. Alternatives include oneZero Hub, Match-Trade bridging, standalone MT4/MT5 bridges that connect to FIX liquidity, and MetaQuotes' own option: MetaQuotes says MetaTrader 5 includes Ultency, a built-in aggregation and matching solution with access to "more than 30 liquidity providers".

Third-party firms also sell managed XCore services. In February 2025, B2BROKER announced PrimeXM XCore support and maintenance services. FXSUPPORT works across bridges, which helps when XCore runs alongside another bridge or you are moving between them. Compare options on our forex bridge solutions and liquidity provider integration pages.

Frequently asked questions