Free MT5 Backtesting MCP Server for Claude
$0.00
Description
Free · Open source (MIT) · Claude / MCP tool
Test the signal it actually made, not a rewrite of it.
MBT is an MCP server that backtests MT5 indicators and Expert Advisors through Claude — by replaying the indicator's own logged decisions against real broker price data, not a separate Python reimplementation that could carry its own bugs. Runs locally, nothing compiled, nothing hidden.
What you actually say to it
“Backtest this indicator on EURUSD 4h for the last year and show me the equity curve.”
backtest“Run the indicator headless over Q1 without opening a chart.”
run_indicator“Compile this EA and run it through the Strategy Tester on GBPUSD.”
compile_ea, run_strategy_tester“Do the EA's actual trades match what the indicator signaled, or did something drift?”
signal_parity“Pull me the raw signals this indicator logged last week.”
get_signals“Break the backtest down by market regime instead of one blended number.”
validate_signalsMBT doesn't design the strategy. It's an MCP toolbox for agentic AI — Claude Code or Claude Desktop — giving it hands in MT5: reading real logged signals, running backtests, compiling and testing EAs. The strategy is still yours, or a skill like ict-analyst you're testing; MBT is what proves whether it actually works before anything trades live.
MCP tools
| Tool | Purpose |
|---|---|
ping | Confirm the terminal is reachable |
get_config | Active terminal and configuration summary |
get_ohlcv | Historical price data for a symbol/timeframe |
get_signals | The indicator's own logged signals — its real decisions |
backtest | Signal replay backtest with full metrics and an HTML report |
validate_signals | Per-regime performance breakdown, where the indicator classifies regimes |
run_indicator | Headless execution over a date range, no chart attached |
compile_ea | Compile an Expert Advisor from source |
run_strategy_tester | Run a compiled EA through MT5's native Strategy Tester |
signal_parity | Compare EA results against the indicator's own signals to catch divergence |
The core idea running through all ten: test what the indicator actually logged, never a parallel guess at what it should have done.
Setting it up
Claude Code
No manual steps — just point your agent at the repo and ask it to set MBT up, e.g.:
“Clone github.com/fxdavid-offbeatforex/mbt and set it up as an MCP server for me.”
It'll clone the repo, install the dependencies, walk you through the config file
(your MT5 terminal path and signal file location), and register itself with
claude mcp add. Ask it to ping once it's done to confirm
the terminal is reachable.
Claude Desktop instead? Settings → Developer → Edit
Config, add an mbt entry to mcpServers pointing at the
same server file, restart.
Full walkthrough (installing MT5, wiring up Claude, MBT's write/execute sibling MTX): how to connect Claude to MT5 →
Requirements
- Python 3.9+
- MetaTrader 5 — native on Windows, or Linux/macOS via Wine
- Claude Code, or Claude Desktop via MCP config
Source & support
MIT licensed, fully open on GitHub — nothing compiled, nothing to trust blindly. Read-only by nature: MBT never places a trade or touches a live account, it only reads and backtests.
View source, issues & updates on GitHubThe other half of the loop
MTX — MT5 Trade eXecutor
Free · Open sourceMBT reads and backtests against real broker data; MTX places and manages what you've already verified here. Together they cover the whole loop — confirm a strategy first, then let Claude execute it, one confirmed trade at a time.
Get MTX
Reviews
There are no reviews yet.