Feature Request: Add /reload-mcps Command for MCP Server Management

Feature Request: Add /reload-mcps Command for MCP Server Management

Summary

Add a /reload-mcps slash command to restart all MCP servers without losing the current conversation context, improving the development workflow when working with MCP servers.

Problem

When developing and testing MCP servers, changes require restarting the MCP servers to take effect. Currently, this means:

1. Lost context: Need to restart entire Claude Code sessions to pick up MCP server changes
2. Multiple session confusion: When running 4+ Claude Code instances simultaneously, it becomes difficult to track which sessions need to be resumed after MCP restarts
3. Workflow interruption: Development iteration cycle is slowed by having to restart sessions and lose conversation history

Proposed Solution

Add a /reload-mcps slash command that:

• Restarts all configured MCP servers
• Maintains the current conversation context and history
• Reloads MCP server configurations from .mcp.json
• Provides feedback on which servers were successfully reloaded
• Handles any MCP server startup errors gracefully

Use Case

Development Workflow:

1. Make changes to MCP server code (e.g., add new tools)
2. Build the MCP server (npm run build)
3. Run /reload-mcps in current Claude Code session
4. Continue testing with updated MCP functionality in same conversation

Benefits

• Improved DX: Seamless MCP development without context loss
• Better productivity: No need to restart multiple Claude Code instances
• Cleaner workflow: Single command handles all MCP reloading
• Context preservation: Maintain conversation history and working state

Current Workaround

Manually restart Claude Code sessions and track which ones need to be resumed - error-prone and time-consuming with multiple concurrent sessions.

---
This request comes from practical experience developing MCP servers and managing multiple Claude Code sessions for different projects.