Differences in MCP Configuration Enablement Status Between Existing and New Projects

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

MCP configuration was disabled for a specific project, yet all these MCPs are enabled by default when a new project is initiated.

Steps to Reproduce

MCP configuration was disabled for a specific project, yet all these MCPs are enabled by default when a new project is initiated.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (Universal)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. This is expected behavior that we may change in one of the upcoming updates.

Current behavior:

  • All configured MCP servers are enabled by default when you open any new project
  • There’s no global setting to disable all servers by default across projects
  • Toggle states (enabled/disabled) are saved per project, so you need to disable unwanted servers each time you open a new project

Related feature request: Consider having all MCP servers disabled by default (instead of enabled)

3

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