Agents cannot find MCP tools

Support Bug Reports
,
1

The agents cannot detect and find active MCP tools.

Version: 2.4.0-pre.46.patch.0
VSCode Version: 1.105.1
Commit: 670f701690eeb27b6643eeee658d3016e0d2bb40
Date: 2026-01-17T23:37:19.378Z
Build Type: Stable
Release Track: Nightly
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

3

I’m having exactly the same issue (Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.8.0-90-generic). It’s odd because some of the MCP tools I have work, and others that I know are present and working on the MCP server side aren’t found. Seems to be a tool discovery / registration issue on Cursor’s side. Looking at the forums, others seem to be affected as well.

1 Like
4

Same issue since today

5

Hey, thanks for the report. This is a known issue. MCP servers connect, but the agent can’t discover them.

Workaround:

  • Open a new chat
  • Ask the agent: “list all MCP tools you have access to”
  • After that, within this session the agent should see the tools
  • You’ll need to repeat this in every new chat

The team is already working on a fix. I added your reports to the tracker. If you need extra diagnostics, you can share the Request ID from the affected chat (three dots in the top right > Copy Request ID).

Related threads:

6

Hey @Travis_Polland, I see you’re on 2.4.0. This version adds a new diagnostic channel for MCP.

Can you share the logs from the Output channel called “MCP File System”? This will help the team investigate the tool discovery issue.

How to find it:

  • View > Output (or Cmd+Shift+U)
  • In the dropdown on the right, select “MCP File System”
  • Copy the contents
7

mcp-log.txt (362.1 KB)

Please see attached + the ChatID is 746e1923-bc5f-4bc7-b24b-b6daf2520dcc

I followed your earlier instructions and created a new chat, and then it worked.

I’m also noticing that MCP servers stop working a lot, and I have to turn them off and back on to work again.

1 Like
8

The same issue is happening for me as well, my cursor details are -
Version: 2.3.41

VSCode Version: 1.105.1

Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30

Date: 2026-01-16T19:14:00.150Z (2 days 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

I even tried removing cursor installation and then performing reinstallation and it didn’t work for me. It has mentioned that the tools aren’t exposed to the server, but cursor settings is showing connected for each mcp server and its has also mentioned that the tools are enabled.

1 Like
9

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.