MT5 Headless Automation

MT5 Headless Automation 🖥️🤖

Run MetaTrader 5 on a server WITHOUT a screen — full EA automation 24/7.

⚠️ Important (read first)

• System-level actions: this skill installs packages (sudo apt), starts Xvfb/Wine, and runs shell scripts. Review before running on production.
• Restarts can interrupt trading: the watchdog auto-restarts MT5 and may terminate EA processes during active sessions — this can detach strategies or affect open positions.
• Credentials: broker login (terminal64.exe via Wine) uses your MT5 account/password. They are entered into the terminal and may appear in process arguments or logs — store them in env vars or a protected file, never in scripts committed to git. Use a read-only/demo account for testing.
• Built from production experience — but backtest/production results are historical and not guaranteed.

What this skill does

1. Install MT5 + Wine + Xvfb (headless display)
2. Log in to broker account (terminal64.exe via Wine)
3. Attach EAs via Navigator (Ctrl+N → OCR → double-click → Enter)
4. Deploy EA changes with 1 command (copy → compile → restart → verify)
5. Monitor heartbeat — auto-restart if the EA hangs
6. Avoid the 5 classic pitfalls (documented below)

Quick start

# 1) Environment
sudo apt install wine xvfb xdotool tesseract-ocr scrot
Xvfb :99 -screen 0 1280x720x24 &
export DISPLAY=:99

# 2) Install MT5 (Windows installer via Wine)
wine "mt5setup.exe" /auto

# 3) Attach EA (scripts/attach_ea.sh)
bash scripts/attach_ea.sh "DRT-Axe"

# 4) Deploy new EA version (scripts/deploy_ea.sh)
bash scripts/deploy_ea.sh

The 5 classic pitfalls (we have hit them ALL)

Files

mt5-headless-automation/
├── SKILL.md
└── scripts/
    ├── attach_ea.sh     # OCR-guided EA attach via Navigator
    ├── deploy_ea.sh     # 1-command: copy → compile → restart → verify
    ├── watchdog.sh      # Heartbeat check + auto-restart
    └── ea_fix.py        # Diagnose why the EA is not trading

Verification (always!)

• EA log: MQL5/Files/_Log.txt (server time GMT+3)
• Heartbeat: _HB.txt — mtime must be < 60 sec old
• Data: _Data.json (real-time klines every 60s)
• ex5 MD5 must match workspace copy after deploy