Local Account Monitor for MT4 & MT5 - Quick Setup Guide and Practical Use
If you run several MetaTrader terminals on the same PC or on the same Windows VPS, it is easy to lose track of which terminal is active, which account is stale, and which setup needs attention.
Local Account Monitor was created to solve that problem in a simple way.
It gives you a clean local overview of multiple terminals without adding trade execution, order management, or copier behavior.
Available versions
MT5 version: https://www.mql5.com/en/market/product/168590
MT4 version: https://www.mql5.com/en/market/product/168591
What the product is designed to do
- Monitor multiple local terminals from one dashboard
- Show which terminals are active and which ones are stale
- Display useful account information in one place
- Make local multi-terminal management easier on one PC or one Windows VPS
What it does not do
- It does not copy trades
- It does not synchronize execution
- It does not open, close, or modify trades
- It is not designed for monitoring terminals across different machines
Two simple modes
1) Agent mode
Attach the product in Agent mode to each terminal you want to monitor.
Each Agent publishes a small local snapshot that contains terminal status and basic account information.
2) Dashboard mode
Attach the product in Dashboard mode to one local terminal.
The Dashboard reads available local snapshots and shows them together in one panel.
Typical setup
- Terminal A - Agent
- Terminal B - Agent
- Terminal C - Agent
- Terminal D - Dashboard
This gives you one place to monitor the local status of the other terminals on the same machine.
How to start quickly
- Open the terminals you want to monitor on the same PC or the same Windows VPS
- Attach Local Account Monitor in Agent mode to each monitored terminal
- Attach Local Account Monitor in Dashboard mode to one terminal
- Wait for one heartbeat cycle
- Check the dashboard panel
What you will see on the dashboard
- Which terminal is updating normally
- Which terminal is stale
- Floating P/L
- Margin information
- Open positions
- Priority order for the most important states
Practical examples
- You run several accounts on one VPS and want a faster local overview
- You want to notice quickly if one terminal has stopped updating
- You want a cleaner way to supervise several local terminals without adding trade-copy logic
MT4 and MT5 together
You can use the MT4 and MT5 versions together in the same local environment. This is useful if your setup includes both platforms on one machine.
When Local Account Monitor is enough
If your main goal is visibility, status checking, and a cleaner local overview, Local Account Monitor is usually all you need.
When you may also need SyncGuard Local Trade Copier
Some traders want more than monitoring. They may also want to copy trades locally between terminals on the same PC or Windows VPS.
That is where SyncGuard Local Trade Copier fits into the workflow.
- Use Local Account Monitor when you want visibility and local supervision
- Use SyncGuard Local Trade Copier when you want local trade copying and execution synchronization between terminals
SyncGuard Local Trade Copier MT5: https://www.mql5.com/en/market/product/159407
SyncGuard Local Trade Copier MT4: https://www.mql5.com/en/market/product/159408
If your setup includes both MT4 and MT5 terminals on the same machine, SyncGuard can also be useful when you want a more active local workflow in addition to monitoring.
Simple product positioning
- Local Account Monitor = local visibility and status overview
- SyncGuard Local Trade Copier = local copying and synchronization workflow
Important note
Local Account Monitor is intentionally focused on visibility and local monitoring. It keeps the workflow simple and read-only.
If later you decide that your local setup also needs copying between terminals, you can check the SyncGuard products above or visit my MQL5 profile: https://www.mql5.com/en/users/thehung21
I hope this guide helps you get started faster and choose the right tool for your local multi-terminal workflow.
