Problem
The MCP server talks to MetaTrader 5 through the MetaTrader5 Python package, which is an IPC client connected to a MetaTrader 5 desktop terminal running on the same host. On Linux, we have to use Wine to get it working (#29) or a Windows VM.
That works, but it's a lot of moving parts and heavy to maintain in the long run:
- a full GUI terminal has to stay running and logged in indefinitely - if it crashes, logs out, or auto-updates, the server goes dark, so it can't run as a clean headless service;
- the Wine bridge / VM is extra infrastructure to stand up and keep alive;
- it pins the server to that one terminal on that one machine;
- if you decide to use multiple broker accounts, you must spawn multiple MT5 terminals.
Proposal
Add an optional, opt-in hosted provider: point the server at a hosted MetaTrader API instead of a local terminal, selected by a single env var. No terminal, no Wine, no VM, no infrastructure to manage.
Implemented in #31 — a TickerAllClient drop-in selected by TICKERALL_API_KEY.
Related: #29
This is the hosted MT5 API being used: https://tickerall.com
Problem
The MCP server talks to MetaTrader 5 through the
MetaTrader5Python package, which is an IPC client connected to a MetaTrader 5 desktop terminal running on the same host. On Linux, we have to use Wine to get it working (#29) or a Windows VM.That works, but it's a lot of moving parts and heavy to maintain in the long run:
Proposal
Add an optional, opt-in hosted provider: point the server at a hosted MetaTrader API instead of a local terminal, selected by a single env var. No terminal, no Wine, no VM, no infrastructure to manage.
Implemented in #31 — a
TickerAllClientdrop-in selected byTICKERALL_API_KEY.Related: #29
This is the hosted MT5 API being used: https://tickerall.com