mql5-docs-mcp
Related Servers
Alternatives to mql5-docs-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with MetaTrader 5 for market data, live streaming, and trading operations, running locally over stdio.-
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with local access to 4500+ MQL5 documentation files and supplementary ebooks via MCP, enabling efficient search, browsing, and error diagnosis for MQL5 development.25MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that bridges AI coding agents with MetaTrader 5 for inspection, market data, MQL5 development, compiling, Strategy Tester review, workspace sync, logs, audit trails, demo trading, and carefully gated live trading.MIT
- AlicenseBqualityBmaintenanceEnables LLM agents to compile, deploy, backtest, and analyze MetaTrader 4/5 MQL sources without touching the MetaTrader UI, leveraging the build pipeline.41MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants and traders to connect to a local MetaTrader 5 terminal, fetch historical market data, run strategy backtests, monitor account status, and manage demo trades via natural language, with an interactive web GUI.2-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to triage BigQuery ML and BigQuery AI tasks, look up exact model and function syntax, and search 137 syntax cards, 14 reference guides, and 104 live-verified narratives via a zero-dependency stdio MCP interface.Apache 2.0
TDQS
Scored across 3 tools
search_reference and get_signature both target function lookups and could be confused at the margins, but the multi-match search vs. single exact-signature semantics are described clearly. explain_code is entirely distinct, targeting return codes and runtime errors.
All three tools use a consistent snake_case verb_noun pattern (search_reference, get_signature, explain_code) with clear, predictable action verbs. No mixing of conventions or styles.
Three focused tools is on the lean side but each earns its place covering search, lookup, and error decoding. Slightly thin for a documentation server that could also expose browsing or content retrieval.
Search, signature lookup, and error explanation are covered, but there is no way to retrieve full documentation text, code examples, or enumerate functions within a section. These gaps force agents to rely only on signatures and external links.