Cursor 2.3.41 not detecting MCP Server tools

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After upgrading to Cursor v2.3.41, MCP Server tool detection has become inconsistent and, in some cases, completely broken.

Although the MCP server runs correctly and is reachable, Cursor does not expose or allow the invocation of any MCP tools.

Broken behaviour: Tools such as whoami, get_design_context, get_variable_defs, etc., are not detected or callable in Cursor v2.3.41.

Steps to Reproduce

  1. Upgrade Cursor to version 2.6.0
  2. Start a valid MCP server with exposed tools
  3. Open Cursor
  4. Attempt to access or call MCP tools
  5. Tools are missing / unavailable

Expected Behavior

Cursor should automatically detect the connected MCP server and expose its available tools, as it did in earlier versions.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

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

For AI issues: which model did you use?

Tried with Auto and other models as well

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes
3

Hey @Hetvee_Sakaria!

  • You’ve mentioned 3 different Cursor versions (2.6, 2.3.41, and 2.3.34) in your post. Which version are you using?
  • What are the status of the MCP servers in your Cursor Settings > Tools & MCP? Red, yellow, green?
  • Can you share a Request ID with privacy mode disabled (Cursor Settings > General > Privacy) for a chat experiencing this behavior? If not, please share screenshots of the chat attempting to use the tools.
4

I had 2.4.14-1769050206 and MCP (with OAuth authentication) failed to load/connect (red) and git repos failed to load.

I downgraded to 2.3.41-1768591662, now MCP works and git repos work.

5
  1. I was facing an issue with the 2.3.41 version. Currently, I’m using 2.3.34.
  2. The status for all the MCP servers is green.
  3. I don’t have the requestID or any screenshot, since I have reinstalled the cursor. But I was facing this issue from 16-Jan-2026 to 19-Jan-2026.
6

Quite a lot has changed around MCP in 2.4, and some issues in earlier versions of 2.4 have been fixed. Please give 2.4.21 a try (you can download it here if it hasn’t rolled out to you). If it’s still not working, please collect logs/screenshots so we can take a look further!

If an MCP shows up as “red”, you can click “Error - Show Output” for the logs.

7

Having the exact same issue still even with the updated version.

What do I do here?
Why does Cursor not see the MCP?
What does the Browser automation mean in Cursor? Is it supposed to do the same stuff as Playwright MCP?

I am heavily relying on this.
Please advise what to do (besides switching to different IDE).

image
image1389Ă—941 67.2 KB

8

Can confirm doesn’t work in 2.4.21 although everything is green.

Agent’s response:

MCP configuration is correct. Mobile MCP tools aren’t available in my tool list, which may require a Cursor restart to load.

Since you asked me to use Mobile MCP tools, attempting the automation workflow. If the tools aren’t accessible, I’ll note what’s needed.

Status:

  • Device connected: Yes (device ID: 97b2dd16)

  • Mobile MCP configured: Yes

  • Mobile MCP tools available: No (not in my tool list)

Next steps:

  1. Restart Cursor to load Mobile MCP tools

  2. Verify the tools appear in Agent mode

  3. Run the automation again

Screenshot 2026-01-23 165626
Screenshot 2026-01-23 1656261071Ă—522 31.1 KB

9

This would be some key info to help us track this down!

10

2.4.21 , not detecting MCP Server tools, i have same problem

11

I also tested this behavior on Cursor v2.4.x, and the issue persisted there as well.

I attempted a full reinstallation of Cursor during troubleshooting, so I no longer have the original request ID available. However, I have shared the confirmed date range during which this issue was consistently reproducible on my machine.

The problem was continuous and not transient, despite reinstalls and version changes.

12

With the latest update, the MCPs seems to be working again.
Thanks!

1 Like