Multiple HTTP MCP servers in one project: Agent only registers one server (call_mcp_tool / available servers)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Description:

I have two HTTP-based MCP servers configured in the same project’s .cursor/mcp.json (e.g. two different JDBC/database MCP endpoints). In Cursor’s MCP UI, both servers show as connected and each reports its tools as enabled (e.g. 14 tools). However, when the Agent runs, only one MCP server is actually available: call_mcp_tool fails for the second server with “MCP server does not exist”, and the error message lists only one available server identifier (e.g. project-0-cursor-mcp-). If I disable ServerA, then ServerB becomes available—without changing ServerB’s configuration—so the issue is tied to running both at once, not a bad URL for either server.

We suspected tool name collisions (both servers originally exposed identical tool names like jdbc_execute_query). We renamed tools on one server (e.g. prefixing with winddb_ so tools are uniquely named vs the other server’s jdbc_*). The problem persists: with both MCPs enabled, the Agent still only sees one server.

Expected behavior: With two distinct MCP entries in mcpServers, the Agent should expose both server identifiers and allow tools to be invoked on each server independently.

Actual behavior: Only one server is registered for the Agent session; the other is missing from the available-servers list until the first is disabled.

Environment: Windows, Cursor [insert version], project-level .cursor/mcp.json with multiple “url”: “http://…/…/mcp” HTTP MCPs.

Workaround: Enable only one database MCP at a time, or use a single gateway MCP that fronts both backends.

Steps to Reproduce

connect to multi http jdbc mcp,example"
{
“mcpServers”: {
“jydbdb”: {
“url”: “http://xxxx.xxx.com/jydb/mcp”
},
“winddb”: {
“url”: “http://xxxx.xxx.com/winddb/mcp”
}
}
}

Operating System

Windows 10/11

Version Information

Version: 2.6.21 (system setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

auto/compose 2 all model

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

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.