Add MCP Server Toggle Interface in Settings

Resolved 💬 2 comments Opened Sep 18, 2025 by boldprojekte Closed Sep 18, 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

Description:
## Feature Request: MCP Server Toggle Interface

### Problem
Currently, managing MCP servers requires CLI commands or editing JSON files, which is cumbersome
when you want to quickly switch between different "modes" of work (backend, frontend, testing,
etc.) in the same project.

Proposed Solution

### Proposed Solution
Add a toggle interface in the Claude Code settings UI that allows users to:

  • ✅ Enable/disable individual MCP servers with checkboxes
  • 🔄 See connection status at a glance
  • 🔌 Reconnect failed servers with a button
  • 💾 Apply changes without restarting Claude

### Example UI
Settings → MCP Servers

□ Supabase (for backend tasks) - Connected
□ Stripe (for payments) - Disconnected☑ Playwright (for UI testing) - Connected
□ Context7 (for documentation) - Connected
☑ Sequential Thinking (for reasoning) - Connected

[Reconnect All] [Apply Changes]

### Benefits

  • Dramatically reduce context usage by only loading needed servers
  • Quick switching between work modes without multiple instances
  • Better UX than current /mcp command or CLI management
  • Maintains existing .mcp.json project configurations

### Use Case
When working on a full-stack project, I might need:

  • Backend work: Only Supabase + Sequential Thinking
  • Payment features: Only Stripe + Context7
  • UI testing: Only Playwright + Supabase
  • Research: Only Context7 + Sequential Thinking

Currently this requires managing multiple Claude instances or frequent CLI commands.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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