MCP Servers Stay in "Loading Tools" forever

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi. When I restart Cursor it’■■■■■ or miss that I will see the MCP Servers showing “Loading Tools” forever. I don’t know if that affects the availability of the servers but I don’t know if that’s a bug or they are simply not loading.

Steps to Reproduce

Start cursor and go to the Tools & MCP section in Cursor Settings

Expected Behavior

Available and Green

Screenshots / Screen Recordings

Screenshot 2025-10-14 at 8.08.37 AM.png
Screenshot 2025-10-14 at 8.08.37 AM.png1076×1924 176 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (Universal)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.1.0

For AI issues: which model did you use?

GPT5 Codex or Med

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
2

Hey, thanks for the report. This is a known issue and the team is already investigating.

To add more context for the team, please:

  1. Open the Output panel Cmd + Shift + U
  2. Select “MCP Logs” from the dropdown
  3. Share any errors that appear when servers are stuck loading

Please also try clearing the cache:
~/.npm/_npx

After that, restart Cursor.

1 Like
3

I am facing the same issue. It is especially noticeable when doing sequential thinking tool call. MCP logs show error without any message, such an error is logged before every sequentialthinking tool call. Behaviour persists even after clearing npx cache, seems a bit better though.

image
image1614×760 42.9 KB

4

In my case it was failing because an invalid refresh token:

2025-10-29 14:08:59.193 [info] Connecting to SSE server
2025-10-29 14:09:01.067 [error] Client error for command Invalid refresh token
2025-10-29 14:09:01.068 [error] Error connecting to SSE server after fallback: Invalid refresh token

I fixed it removing the MCP tool and re-adding it, which cleared the invalid token and prompted me to reconnect/reauthenticate the tool via OAuth.