AI Assistant MCP in MT5 Beta Build 6194 has no file read tools - page 3

 
Molenweg3 #:
i have it also the same problem
I tried re-entering the API key in the AI assistant on MetaTrader 5

https://www.mql5.com/en/users/youraccount/api (re-entry to MetaTrader 5) and restart MetaTrader 5 and MetaEditor. And then it worked for me, you can give it a try. Or something like installing Finex MetaTrader 5/Monex MetaTrader 5
 
Alain Verleyen #:

Thank you. It's already working for me as I mentioned in Post #19.

I probably should have been more detailed as to the specific issues. Sessions were stalling, going in circles on repeat, and stacking up by spontaneously resurrecting themselves. Renat's diagnosis certainly explains that.

 

Just as additional information, I had a very similar situation, which is how I found this thread.

Even a simple “hello” took a long time to get a response because of checks such as get_workspace_info . For slightly more complex requests, the session would repeatedly retry and eventually time out.

I deleted the " llm-agent " folder and restarted MT5. All previous session history was lost, but the AI Assistant started responding quickly again.

I then restored the backed-up files, and it has continued to work normally.

Perhaps something was reset by deleting the folder, although I have no way to confirm the cause. This is only what I observed in my own environment, but I thought it might be useful as a reference.

 
Sajiro Yoshizaki #:

Just as additional information, I had a very similar situation, which is how I found this thread.

Even a simple “hello” took a long time to get a response because of checks such as get_workspace_info . For slightly more complex requests, the session would repeatedly retry and eventually time out.

I deleted the " llm-agent " folder and restarted MT5. All previous session history was lost, but the AI Assistant started responding quickly again.

I then restored the backed-up files, and it has continued to work normally.

Perhaps something was reset by deleting the folder, although I have no way to confirm the cause. This is only what I observed in my own environment, but I thought it might be useful as a reference.

For the record, deleting the folder was ineffective on my end. The only thing that fixed it was Alain's report to the Admin's and the Admin's subsequent fix. Such a problem residing on the LLM router can't be fixed from the client-side.

Forum on trading, automated trading systems, and trading strategy testing

New MetaTrader 5 Platform Build 6180: More AI Features

Renat Fatkhullin , 2026.09.15 17:38

There was a problem with the LLM router overload due to the load in the last 3 days.

Please try it now.