MCP server for MetaTrader 4/5 build pipeline — compile, deploy, backtest, parse reports
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-mt5","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-mt5 > **Model Context Protocol server for the MetaTrader 4/5 build pipeline.** > Compile MQL sources, deploy compiled EAs, run Strategy Tester, parse reports, tail logs — all driven by an LLM agent without touching the MetaTrader UI. [](https://github.com/PHUICMT/mcp-mt5/actions/workflows/ci.yml) [](https://www.python.org/) [](LICENSE) [](https://www.metaquotes.net/) --- ## What this is — and what it isn't | ✅ This server | ❌ Not this server | |----------------|--------------------| | MetaTrader **dev harness** — compile, deploy, backtest, parse | Live trading (orders, positions, quotes) | | Wraps `MetaEditor64.exe` / `terminal64.exe` CLI directly | Wraps the `MetaTrader5` Python package | | Runs entirely offline against installed terminal | Connects to a broker server | | Iterates strategies *before* they go live | Executes strategies in production | > **Use case:** an LLM agent edits `.mq5` source → compiles → deploys → runs Strategy Tester → reads report → adjusts → repeats. No broker login, no human in the loop, no risk of real-money execution. For runtime trading, pair this with a live-trading MCP — they target different layers and compose well. --- ## Tools 27 tools (plus 16 deprecated aliases until 0.6.0) and 2 resource templates. Every tool carries MCP annotations (read-only / destructive hints), a typed output schema and per-parameter descriptions; failures are reported as tool errors, never as a normal result with an `error` key. ### 🔍 Discovery & terminal selection | Tool | Description | |------|-------------| | `env_info` | Resolved paths, terminal hash, edition, and missing-component issues | | `list_terminals` | Every MT4/5 terminal data folder under `%APPDATA%\MetaQu…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.