From nothing to a live desk, in order

Quick start

Two commands and one browser tab. This assumes a Windows machine with at least one MetaTrader terminal already logged in.

$ UltimateCoreX.exe$ start http://127.0.0.1:8040

• The hub listens on your own machine only until you decide otherwise
• The database file is created next to the program on first run
• Closing the window stops the hub — nothing keeps running in the background

Requirements

Deliberately modest. If it runs your terminals, it runs the hub.

Install the hub

The hub is a single executable. There is no installer ceremony and no runtime to chase.

$ [Convert]::ToBase64String((1..32|%{Get-Random -Max 256}))

• Copy the program to a folder you control, for example C:\UltimateCoreX
• Run it once — the database file and configuration are created beside it
• Open the console at http://127.0.0.1:8040
• To protect remote access, put a long random string in apitoken.txt next to the program

Local terminals

MetaTrader 5 terminals on the same machine as the hub need no extra software.

• Open the terminal picker in the console and select the terminal to read
• The account appears on the roster with equity, positions and history
• History is rebuilt in the background — thousands of closed trades, not the recent few
• MetaTrader 4 installations are skipped automatically; use the reader program instead

Remote servers

Each trading server runs the same program in agent mode. It reads local feed files and posts them outward — it never accepts an inbound connection.

$ UltimateCoreX.exe --agent --hub https://your-hub --token PASTE_TOKEN --interval 5

• The server appears as online within a few seconds
• Its accounts are tagged to it automatically
• The agent reconnects on its own after a restart or a dropped link
• A wrong token is rejected outright — nothing is stored

MetaTrader 4 accounts

MetaTrader 4 cannot be read programmatically, so the account publishes itself through a reader program the platform generates for you.

• Generate the reader from the deployment section of the console
• Copy it into the terminal's Experts folder and refresh the navigator
• Attach it to any single chart and allow automated trading
• The account appears on the roster, marked as connected through a reader

Copy trade

The platform generates both sides of the copier and then measures how faithfully the copy is working.

• Generate the sender for the master account and the receiver for each follower
• Both sides share a channel name so several groups can run side by side
• The receiver maps positions by identity and normalises volume and stop levels per broker
• A persistent drawdown kill switch stops the follower and survives a terminal restart
• Regenerate and redeploy after an upgrade so every follower gets the latest fixes

Alerts

Alerts go to Telegram, because that is where people actually look.

• Create a bot with BotFather and get its token
• Get your chat identifier from any userinfo bot
• Paste both into notification settings and press the test button
• Choose which events matter: drawdown, thin margin, silent account

Freeze and control

Control is off until you turn it on, and even then it can only do one thing: stop new entries.

• Freeze scope is global, per server, or per account
• Frozen means no new positions — open ones still exit with the master
• Instructions are written atomically so a robot never reads a half-written command
• State survives restarts on both sides
• Automatic news pausing writes the same instruction and clears it afterwards

API reference

Every screen in the console is built on the same endpoints. From outside the machine they require the bearer token.

$ curl -H "Authorization: Bearer $TOKEN" https://your-hub/api/accounts

Command line

The same executable is the hub, the agent and the internal worker. The mode is a flag.

Troubleshooting

The five things that actually go wrong, and what they mean.