MCP Servers not recognized in v2.3.4 / v2.4.2 (npx deployment)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi Team,

We’ve noticed a connectivity issue in the latest versions (v2.3.4 and v2.4.2) regarding MCP servers added via npx.

The Problem: Despite the servers appearing to be configured correctly, the bot is unable to access the MCP server scope.

Observations:

Status Indicators: Servers are enabled (indicated by the green icon).

Logs: The logs are clean and confirm that the servers are running successfully.

Connectivity: The bot fails to recognize or connect to the available tools/functions within the MCP scope.

Could you please look into whether there is a regression affecting npx-based server recognition in these specific builds?

Steps to Reproduce

Just find any MCP server using npx and add it to the list of MCPs

Operating System

MacOS

Version Information

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Tested with different models

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report.

Looks like a known issue that showed up in version 2.3.41 - MCP servers appeared connected, but the agent couldn’t see their tools. It got fixed end of January.

Your version (2.3.34) is older than when the bug started. Can you clarify:

  • When exactly did the issue start?
  • Did you try updating to the latest stable version?

If the problem sticks around after updating, try this workaround:

  • Open a new chat
  • Ask the agent: “list all MCP tools you have access to”
  • After that, the agent should see the tools in this session

For debugging, I need the Request ID from the broken chat (three dots top right in chat > Copy Request ID). Can you share it?

Related threads with the same issue (already resolved):