MCP Servers Not Detected on Initial Runs of main.py; Tools Recognized Only After Multiple Restarts

Describe the bug
When running main.py, the MCP client frequently fails to detect and connect to available MCP servers on the first few attempts. The tool discovery and response handling only begin working correctly after restarting the script 3–4 times. This seems to indicate a race condition or delay in server registration or discovery.

To Reproduce
Steps to reproduce the behavior:

Start the MCP servers.

Immediately run main.py.

Observe that no tools are identified or invoked.

Stop main.py and restart it.

Repeat 3–4 times until it begins identifying tools and responding as expected.

Expected behavior
The MCP client should detect available MCP servers and tools correctly on the first run of main.py, assuming the servers are already running.

IM GETTING RESPONSE FROM LLM IT CANT IDENTIFY TOOLS THAT ARE UN SERVER JSON FILE BUT AFTER SOME RETRIES LIKE JUST RUNNING AND EXITING MAIN.PY RANDOMLY THE SERVERS ARE IDENTIFIED AND IT WORKS PROPERLY

Start by running the MCP servers and main.py as described, using the server JSON configuration mentioned in the report. Trace the initial server registration, discovery, and tool-response flow to determine why the first run misses available tools. Done means main.py detects and invokes the configured tools on its first run without repeated restarts.