TradingView to MetaTrader 5 Webhook Bridge
A production-oriented desktop bridge from TradingView webhooks to MetaTrader 5 execution.
Split agent/UI architecture with a SQLite write-ahead queue, dual-auth intake, event dedupe, and open/close/reverse execution.
- Split agent/UI architecture for a desktop bridge
- SQLite write-ahead-log queue for durability
- Dual-auth intake plus event-ID deduplication
- MT5 adapter executes open, close, and reverse commands
A production-oriented Windows desktop bridge that turns TradingView webhook alerts into MetaTrader 5 orders. It uses a split agent/UI architecture, with a SQLite write-ahead-log queue for durability, dual-auth webhook intake, and event-ID deduplication so a retried or duplicated alert never fires twice. The MT5 adapter executes open, close, and reverse commands.
The design tackles the real pain points of alert-to-broker automation on MT5: durability across restarts, authentication, and idempotency. It is a practical alternative to paid connector services, built to be run by an individual trader on their own machine. Durability across restarts and deduplication of repeated alerts are what separate a hobby script from something you can leave running against a funded account, which is the standard this bridge was built to.
Executes live broker orders; shared as engineering work, not financial advice. No profit is promised and users trade their own accounts at their own risk.
Automation is infrastructure, not financial advice. No profit guarantees. Every live system needs staged testing, risk limits, and owner approval.