Hey, thanks for the re-report. I see the original bug was marked as fixed, but it looks like the issue came back in 3.0, I’ll pass this to the team.
Can you send fresh logs from the MCP Output Panel View → Output → select MCP in the dropdown while reproducing on 3.0.13? I want to check if it’s the same pattern with parallel CreateClient/ListOfferings, or if the behavior changed.
For now, toggling it off and on is a workaround. I know it’s annoying, but at least it works.
The original was closed after the team was informed, it has never been fixed. It’s been closed maybe six times over many months in fact, despite never being fixed.
You have, somehow, managed to make it even worse in version 3.0 !!
In addition to all the bugs that have never been fixed in your MCP code, it now also does not reload the tools when you change your config (It incorrectly lists the old tools that it first loaded instead of refreshing its list).
This is getting very frustrating because I have explained very clearly exactly what your bug is (calling an async function in a loop by mistake, thus spawning a storm of simultaneous connections which never close, because you’ve discarded all their handles) and how to fix it, and nobody ever does anything!