Hello,
I am experiencing a reproducible MetaEditor AI Assistant MCP issue on Build 6230.
Problem:
metaeditor5__get_workspace_info consistently fails with:
-32603: request timeout after PT300S
Because get_workspace_info is the mandatory pre-flight step, the AI Assistant cannot proceed to file access, compilation, patching, or other MetaEditor MCP operations.
Environment:
- Windows 10
- MetaTrader 5 / MetaEditor Build 6230
- goose 1.48.0
- Provider: MQL5 Lite
- System Proxy disabled
- WinHTTP proxy disabled
- VPN tested without effect
Reproduction:
1. Start MetaTrader 5 and MetaEditor.
2. Open a new AI Assistant chat.
3. Select MQL5 Lite.
4. Ask:
Call get_workspace_info on MetaEditor now.
Do not call MetaTrader.
5. The MCP call starts, but after approximately 300 seconds it returns:
-32603: request timeout after PT300S
Diagnostics:
- 127.0.0.1:22345 is listening.
- 127.0.0.1:22346 is listening.
- Test-NetConnection succeeds for both ports.
- curl to /mcp returns HTTP 401 immediately on both ports.
- goose establishes TCP connections to both local MCP ports.
- File permissions were checked and the user has FullControl.
- The issue reproduces in both XMTrading MT5 and a clean official MetaQuotes installation.
- Updating from Build 6209 to Build 6230 did not resolve it.
MetaEditor log shows repeated:
127.0.0.1 get workspace environment
but the request never completes.
goose logs also show:
could not parse JSON response as ServerJsonRpcMessage,
treating as accepted: error decoding response body for url
(http://127.0.0.1:22345/mcp)
The same warning has also appeared for port 22346.
Could someone from MetaQuotes please confirm whether this is a known MCP issue or reproduce it on Build 6230?
- MetaTrader 5 build 6140 - MCP internal server returns 401 Unauthorized with generated API key
- MetaTrader 5 Beta Build 5955: MCP and Agentic AI support
- Webrequest switches to https after 2 minutes.
取引の機会を逃しています。
- 無料取引アプリ
- 8千を超えるシグナルをコピー
- 金融ニュースで金融マーケットを探索