MetaTrader 5 feeds
Where a MetaTrader 5 server gets its prices.
MT5 can receive prices through data-feed processes, gateways, and custom integrations. The important decision is which route owns each instrument.
- Data feeds and gateways serve different roles.
- Feed processes can be separated from the history server.
- Provider rights and symbol mappings remain the broker’s responsibility.
Choose the route
Decide whether each instrument enters through a feed, a gateway, or a managed integration before configuring priority.
Separate when useful
Remote or service-based feed processes can isolate provider connectivity from the history server.
Match the data model
An OTC Bid/Ask stream and an exchange feed with Last, volume, and depth are different source requirements.
On this page
MT5 offers more than one server-side route for market data. A data feed is usually the direct path for quotes, news, ticks, and books from a provider. A gateway connects the platform to an external trading system and may bring prices as part of that wider relationship. Custom integrations can publish a managed or broker-owned price stream.
Data-feed processes
An MT5 data-feed process connects to a source and passes supported market data to the history server. Depending on the module and deployment, it may run locally, remotely, or as a service.
Separating the process can reduce coupling with the history server, but it adds an endpoint, service account, network path, monitoring target, and recovery procedure. Treat it as an architectural choice, not simply an installation option.
Ready-made modules do not include the data
A supplied or compatible module can shorten integration work. It does not grant:
- a provider account;
- instrument entitlements;
- exchange or redistribution rights;
- permission to use prices outside the agreed environment; or
- support for every data type the provider offers.
Confirm Bid/Ask, Last, volume, Market Depth, news, and symbol-reference data separately.
Gateways can also own the price
Where a gateway supplies an instrument, its pricing route can take precedence over ordinary feed selection. That makes gateway ownership a first-order design decision.
Before adding a data feed for the same symbol, establish which component should be authoritative and how a gateway outage changes the result. Avoid applying symbol renaming or price shifts independently in both routes.
Custom and managed sources
The platform’s integration interfaces allow a broker or provider to bring in a controlled price stream. This is appropriate when prices are aggregated, calculated, protected, or normalized before MT5 receives them.
The integration must still define:
Swipe or scroll horizontally to see all columns
| Concern | Decision |
|---|---|
| Instrument identity | Provider name, MT5 path, digits, point size |
| Data types | Bid/Ask, Last, volume, book, statistics |
| Time | Source timestamps, server time, sessions |
| Continuity | Primary, backup, reconnect, stale-data policy |
| Evidence | Raw input, accepted output, journal, alerts |
Select by instrument, not by brand
An OTC currency pair may need only a resilient Bid/Ask stream. A futures or equities product may require Last, trade volume, and authentic Market Depth. Start with the instrument’s data model and rights, then choose the module or gateway.
MT5 feed settings cover symbol scope and mappings. Market Depth and ticks cover the richer data model.
A feed shaped around your setup
Choose the MT5 entry point deliberately.
Tell us which module or gateway you use today and which instruments matter. We’ll set out how a managed feed can attach.