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

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!

13

The same issue is happening for me on 2.4.21, MCP Tools is configured and green still the chat Agent is not able to connect to it, so it ends trying to execute itself commands instead of using the MCP (Jenkins and Jira ones in my case)

In the meantime, I have updated to 2.4.28 and it works again !!

14

I have the same issue on version 2.4.31. When i try restarting cursor, my MCP servers are showing “No tools, prompts, or resources”

After some time tools will start showing up but agent context does not have access to them and it still fails.

image
image758Ă—246 20.8 KB

While the tools are showing up as enabled, I’m seeing this when i ask cursor to use MCP:

image
image762Ă—260 21.4 KB

Request ID: 64d167f8-031b-4c28-b274-29e2dd2b2874

15

Hey all!

We’ve made a lot of changes in 2.5, specifically implementing Dynamic Context Discovery for MCP servers.

Please give 2.5 a try. If you haven’t been auto-updated you can download it from Cursor · Download.

16

Still experiencing intermittent MCP tool visibility on macOS (post-2.5 update, Version: 2.5.25 (Universal))

I’m on macOS (Darwin arm64 25.2.0) and still experiencing this issue even after updating. The behavior is intermittent:

Symptoms:

  • MCP servers are configured correctly in ~/.cursor/mcp.json (4 servers: MCP_DOCKER, Figma Desktop, SLACK_MCP, shakebugs)

  • Servers may show as green in Cursor Settings > Tools & MCP

  • After Cursor reload/restart, tools briefly become available

  • Tools disappear from agent context shortly after

  • Currently, only 1 of 5 configured MCP servers (context7 plugin) is visible to the agent

Environment:

  • macOS Darwin 25.2.0 (arm64)

  • Mix of local MCP servers (docker command, localhost URL) and remote MCP servers (HTTPS URLs)

  • Docker Desktop is running (for MCP_DOCKER)

The Dynamic Context Discovery introduced in 2.5 doesn’t seem to maintain persistent visibility of MCP tools. The “discovery” appears to happen at session start but doesn’t reliably persist or re-discover when tools become unavailable.

17

I’m seeing a similar issue to what Woofych reported with MCP tools not being exposed

My symptoms:

  • MCP server is configured correctly in ~/.cursor/mcp.json (command-based stdio server using npx tsx)
  • Server shows as green/connected in Cursor Settings > Tools & MCP
  • Tools are discovered and cached (logs show “Found 1 tools”, tool appears in mcp-cache.json)
  • Tool is not visible to the AI assistant despite being cached and the server showing as connected
  • Manual invocation of the tool via the MCP bridge script works correctly, confirming the server and tool function properly

Environment:

assistant.Version: 2.5.26
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Like the other report, tools are discovered but not reliably exposed to the agent. The server stays connected and tools are cached, but the assistant cannot access them.