URGENT: Claude Code CLI MCP reload broken for 6+ months - blocking all MCP development

Critical Issue: MCP Server Development Blocked

This issue has been reported multiple times (#3095, #2756) since June 2025 with no resolution. It's completely blocking MCP server development with Claude Code CLI.

The Problem

1. MCP servers don't reload when code changes - Python modules stay cached in memory
2. /mcp disconnect/reconnect doesn't work - Doesn't actually reload the Python modules
3. Must fully restart Claude Code CLI - Losing entire conversation context every time
4. Every single code change requires full restart - Making development nearly impossible

Impact

• Cannot effectively develop MCP servers with Claude Code CLI
• Wastes hours daily on restarts
• Forces developers to abandon CLI for Desktop or give up entirely
• This is a REGRESSION - Claude Desktop has working hot reload

Current Workarounds (All Inadequate)

• Exit and restart with claude --continue (loses context)
• Kill Python processes (doesn't work - CLI restarts with cached modules)
• Use sys.modules tricks (unreliable with dependencies)

Why This Matters

Claude Code CLI is advertised as a development tool, but it's unusable for MCP development - one of its key features. Meanwhile, Claude Desktop has multiple hot reload solutions (mcp-hot-reload, mcpmon, etc.).

Requested Fix

Add a proper MCP reload command that:

1. Kills the Python MCP process
2. Clears all cached modules
3. Restarts with fresh code
4. Maintains conversation context

Or at minimum, make /mcp actually restart the process instead of just reconnecting.

Timeline

This has been broken for 6+ months since June 2025. The community needs this fixed urgently.

Testing MCP servers with Claude Code CLI currently requires:

• Write code
• Save file
• Exit Claude completely
• Restart with claude --continue
• Reconnect MCP
• Test change
• Repeat for EVERY change

This is not sustainable for development.