get_account_info
Get MetaTrader 4 account information
LABSCO SUMMARY
This can place orders. Everything else about it is secondary to that.
Backtesting and remote Expert Advisor compilation are genuinely useful — the edit-compile-test loop in MT4 is miserable, and doing it from an editor is a real gain. But the same connection places market orders against a live account, and there is no read-only mode described. If you connect it, connect it to a demo account until you have watched what it does. The file-based fallback is a nice touch that says the author has seen the HTTP bridge fail mid-session.
What it is
A bridge to MetaTrader 4, connecting through an HTTP endpoint and a companion Expert Advisor running inside the terminal, so a server on one machine can drive MT4 on another.
What you get
- Account information — balance, equity, margin
- Live market prices for symbols
- Placing market and pending orders; viewing and closing positions
- Trading history
- Backtesting Expert Advisors with detailed configuration
- Remote Expert Advisor development — create, edit, sync and compile, with compilation errors reported back
- A file-based fallback for status and results when the HTTP path fails
Requirements
A MetaTrader 4 terminal with the companion Expert Advisor installed, plus Node for the server. The two can be on different machines — their documented setup runs the server on Linux against MT4 on Windows.
Setup effort
Build from source — git clone https://github.com/8nite/metatrader-4-mcp.git
USE CASES
01
Iterating on an Expert Advisor
Edit, sync and compile remotely, with errors reported back.
02
Testing a strategy
Backtests with real configuration.
03
Watching an account
Balance, equity, margin and open positions.
14 tools
Listed in project code.
get_market_data
Get current market data for a symbol
place_order
Place a trading order in MetaTrader 4
get_positions
Get all open positions
close_position
Close an open position
get_history
Get trading history
run_backtest
Run a backtest on an Expert Advisor
get_backtest_results
Get results from the last backtest
list_experts
List available Expert Advisors for backtesting
get_backtest_status
Get the current status of a running backtest
sync_ea
Upload EA file to MetaTrader 4 for compilation
compile_ea
Compile an EA on MetaTrader 4 and get compilation results
list_local_eas
List EAs in the local development folders
sync_ea_from_file
Sync an existing EA file to MetaTrader 4
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools registered in the project's code.
Requires
- Node.js on the machine running the MCP server
- A Windows machine running MetaTrader 4, with Node.js for the HTTP bridge
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/8nite/metatrader-4-mcp.git
cd metatrader-4-mcp
npm install
npm run buildOn the Windows machine that runs MT4: copy the windows-server/ folder over, install Node.js, then run npm install and npm start inside that folder — the HTTP bridge starts on port 8080
Copy mcp/MCP_Ultimate.mq4 into your MT4 MQL4/Experts/ folder, compile it in MetaEditor, attach it to any chart, and make sure "Allow DLL imports" is enabled in MT4 settings
Add the configuration under MCP Clients to Claude Code, with the absolute path to dist/index.js in your clone and MT4_HOST set to the IP of your Windows machine
MCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"mt4-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_METATRADER_4_MCP>/dist/index.js"
],
"env": {
"MT4_HOST": "192.168.50.161",
"MT4_PORT": "8080"
}
}
}
}<YOUR_PATH_TO_METATRADER_4_MCP> is the folder you cloned and built. 192.168.50.161 is the author's own LAN address (the server's default) — set MT4_HOST to the IP of the Windows machine running the HTTP bridge. 8080 is the bridge's port.
