[FEATURE] Disable individual MCP servers globally

Resolved 💬 3 comments Opened Nov 20, 2025 by fabb Closed Nov 20, 2025

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I have some MCP servers I rarely use but that use a lot of context (e.g. chrome-devtools). They should be disabled by default, also in new projects, and only enabled manually on demand.

Proposed Solution

Currently there is only a project-local setting to disable individual MCP servers. That means, I have to turn them off for each project, and each new project. Since that is cumbersome, I suggest to allow to disable individual MCP servers globally, and be able to enable it only in projects where I need them on-demand.

Alternative Solutions

I could also add/remove the MCP server every time I want to start/stop using it, but that's cumbersome.

I could add MCP servers only to local projects, but that is annoying too.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗