Engineering guide
How to Build an MT5 Trading Bot with Python
The steps from a first connection to a multi-strategy system you can trust with real money, based on a desk we automated.
- Strategies live in our MT5 build
- 10
- Paper trading before go-live
- 2 weeks
- From kickoff to all strategies live
- 11 weeks
A Python bot for MetaTrader 5 can be written in an afternoon: connect, read prices, send an order. Making it safe to run unattended is the real work. This guide covers both, in the order we build them for clients.
It draws on a system we built for a prop trading desk that now runs 10 strategies live on MT5, with 20% less slippage per fill than manual execution. Nothing here is investment advice, and no code can make a losing strategy profitable.
The steps
- 1. Connect
- Run the MT5 terminal, enable algorithmic trading, then call mt5.initialize() and check mt5.account_info() and mt5.last_error() before doing anything else.
- 2. Read market data
- Use copy_rates_from_pos or copy_rates_range for bars and symbol_info_tick for the latest bid and ask. Load them into pandas for indicator work.
- 3. Write the signal as a pure function
- Given data, return buy, sell or hold with a size. Keeping it free of order code makes it testable and lets you backtest the exact same logic.
- 4. Execute separately
- An execution module turns signals into order_send requests (symbol, volume, type, price, deviation, magic number, filling mode), checks the result code, and records the fill price.
- 5. Add risk limits above every strategy
- Exposure, daily loss, position count and correlation limits that can block any order, across all strategies at once.
- 6. Paper trade in parallel
- Run against a demo account alongside the intended live setup for at least a couple of weeks and compare fills and behaviour.
- 7. Monitor and stop safely
- A dashboard of positions, P&L and slippage, alerts on errors, and a kill switch that flattens or freezes trading when data or connectivity is wrong.
Architecture for more than one strategy
Components of the multi-strategy system we shippedScroll horizontally to compare all columns.
| Component | Why it exists |
|---|---|
| MT5 connector | One place that owns the terminal session, reconnects, and normalises errors |
| Strategy modules | Each strategy produces signals only, so adding one does not touch execution |
| Cross-strategy risk manager | Built first; without it every new strategy needs its own manual risk review |
| Parameter service | Change settings from the dashboard without restarting the engine |
| Slippage attribution | Shows whether a poor result came from the signal or the execution |
| Dashboard | Updates about one second after each fill |
Mistakes that cost real money
- Mixing signal and order code, so backtests and live trading run different logic.
- Ignoring the order_send result code and assuming every order filled at the requested price.
- No limit across strategies, so two strategies double the same exposure.
- Skipping paper trading. In our project, two weeks of parallel paper trading caught two race conditions that would have caused real losses.
- Running on a home computer. Use a VPS close to the broker's servers, with monitoring and restarts.
Frequently asked questions
- Python or MQL5 for an MT5 bot?
- MQL5 Expert Advisors run inside the terminal and suit a single strategy. Python suits multi-strategy systems, data science libraries and dashboards. Many production systems use both.
- Does the MetaTrader5 Python package work on Mac or Linux?
- It talks to a running MT5 terminal, which is a Windows application. Most teams run it on a Windows VPS; other setups add compatibility layers and more things that can break.
- Can a bot guarantee profits?
- No. A bot follows rules exactly and quickly. Whether those rules make money depends on the strategy and the market, and past results do not predict future ones.
- Can you build this for us?
- Yes. See our MT5 trading bot development service, or book a free consultation for a written plan and a fixed quote.
Sources and scope
This is an engineering planning guide, not investment advice. Requirements depend on the product and deployment. Consult the relevant authorities and qualified advisers before launch.
- MetaTrader 5 Python integration documentation
Official reference for initialize, copy_rates, symbol_info_tick and order_send.
Planning your MT5 trading bot development project?
Bring your workflow, integration requirements, and deployment constraints. We will identify the discovery work, specialist reviews, and dependencies needed for a realistic delivery plan.
