Thanks for the detailed report. This is a known issue where Cursor’s agent session fails to register multiple MCP servers simultaneously, even though both appear connected in the MCP settings UI.
A similar issue was reported and acknowledged earlier – a partial fix shipped in a previous version, but it was only confirmed for local (STDIO) servers. Your setup uses HTTP-based servers, which may not have been covered by that fix.
To help narrow this down, could you check the MCP output logs for each server? Go to View > Output, then select MCP: jydbdb and MCP: winddb from the dropdown. If both show as connected with tools listed, the issue is in how the agent session receives the server list. If one shows errors, that would explain why the agent only sees one.
Also, could you try starting a new chat session after both servers show as connected in the MCP settings? Tool routing can sometimes be cached per session.
Your current workarounds (using one server at a time, or a single gateway) are the best options while we work on this. I’ve flagged this with our team.