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

Additional note: If there's a different way to properly reload MCP servers in Claude Code CLI that I'm missing, please let me know ASAP. I've tried:

• /mcp disconnect and reconnect (doesn't reload Python modules)
• Killing Python processes (CLI auto-restarts with cached modules)
• Using claude mcp remove then claude mcp add (corrupts config over time)
• Adding sys.modules cleanup in the MCP server (partially works but unreliable)

If there's a proper workflow for MCP development with Claude Code CLI that actually allows code changes to be reflected without full restart, please document it.

Currently spending more time restarting than coding.

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/3095
2. https://github.com/anthropics/claude-code/issues/2756
3. https://github.com/anthropics/claude-code/issues/605

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This issue should remain OPEN until there is an actual fix implemented.

Similar issues closed without solution:

• #2756 - "Add /reload-mcps Command" - Requested June 2025, closed July 31 by @ollie-anthropic without providing any solution or explanation
• #3095 - "MCP Server Cache Not Refreshing" - Open since July 2025, only community workarounds provided, no official fix

Impact:

This is a critical development blocker that has been affecting MCP developers for over 6 months. Closing this as a duplicate without fixing the underlying issue just hides the problem.

Current state:

• The /mcp disconnect/reconnect command does not reload Python modules
• The only working solution is to completely exit Claude Code and restart with claude --continue
• This breaks the development flow and loses conversation context
• Developers spend more time restarting than coding

What we need:

An actual MCP reload mechanism that:

1. Kills the Python process
2. Clears module cache
3. Restarts with fresh code
4. Maintains conversation context

Please do not close this issue until a working solution is implemented and documented. The community has been asking for this basic development feature since June 2025.

Specific Solution Required

For me and other MCP developers, a real solution would be:

A single command that Claude Code CLI can execute itself (either as a slash command or internally) that:

1. Disconnects the MCP client connection
2. Kills the MCP server process completely
3. Clears all cached Python modules
4. Restarts the MCP server with fresh code
5. Reloads new commands and tools
6. Reconnects automatically to Claude Code CLI
7. Maintains the conversation context

The Critical Point:

Claude Code CLI should be able to do this ITSELF - either through:

• A slash command like /mcp-reload that Claude can execute
• An internal mechanism that Claude can trigger
• A command that doesn't require manual user intervention

Current Reality:

As far as we've found, there is NO WAY for Claude Code CLI to reload MCP servers without:

• Stopping development completely
• Losing conversation context and directions
• Manually exiting and starting over with claude --continue
• Breaking the entire development flow

Why This Matters:

When Claude is helping develop an MCP server, it needs to be able to test changes immediately. Currently, Claude can:

• Write the code ✓
• Save the files ✓
• Build the project ✓
• But CANNOT reload the MCP to test ✗

This makes Claude Code CLI essentially unusable for MCP development. We need a command that Claude itself can execute to reload MCP servers without human intervention.

Please implement a proper reload mechanism that works within the active session. This has been the #1 blocker for MCP development for over 6 months.

Specific Solution Required

First, I want to thank the Anthropic team for their incredible hard work on Claude Code CLI. It's an amazing tool that has transformed how we develop software. I truly appreciate all the effort that goes into making Claude as capable as it is.

However, this MCP reload issue must be addressed now for those of us using Claude Code CLI to develop MCP servers.

A real solution would be:

A single command that Claude Code CLI can execute itself (either as a slash command or internally) that:

1. Disconnects the MCP client connection
2. Kills the MCP server process completely
3. Clears all cached Python modules
4. Restarts the MCP server with fresh code
5. Reloads new commands and tools
6. Reconnects automatically to Claude Code CLI
7. Maintains the conversation context

What is NOT a Solution:

• Having the user manually execute commands ✗
• Having to exit Claude Code CLI to reload ✗
• Any workaround that breaks the development flow ✗
• Solutions that require human intervention ✗

These are not acceptable because they defeat the entire purpose of having Claude assist with development.

The Critical Point:

Claude Code CLI must be able to do this ITSELF - either through:

• A slash command like /mcp-reload that Claude can execute
• An internal mechanism that Claude can trigger
• A command that doesn't require manual user intervention

Current Reality:

As far as we've found, there is NO WAY for Claude Code CLI to reload MCP servers without:

• Stopping development completely
• Losing conversation context and directions
• Manually exiting and starting over with claude --continue
• Breaking the entire development flow

Why This Matters:

When Claude is helping develop an MCP server, it needs to be able to test changes immediately. Currently, Claude can:

• Write the code ✓
• Save the files ✓
• Build the project ✓
• But CANNOT reload the MCP to test ✗

This makes Claude Code CLI essentially unusable for MCP development. We need a command that Claude itself can execute to reload MCP servers without human intervention.

I know you're all working hard and have many priorities, but please understand that this has been the #1 blocker for MCP development for over 6 months. Those of us trying to build MCP servers with Claude Code CLI need this addressed urgently.

Thank you for your time and for all the amazing work you do. Looking forward to a solution that makes MCP development viable with Claude Code CLI.

CORRECTION - Critical Clarification

I need to correct my previous comment. When I mentioned a slash command, that's NOT what we need.

What We Need:

Claude Code CLI must be able to reload MCP servers BY ITSELF internally - not through user-executed slash commands.

The Problem with Slash Commands:

• Slash commands like /mcp-reload still require THE USER to type them ✗
• This is NOT a solution ✗
• Claude cannot execute slash commands on its own ✗

The ACTUAL Solution Required:

Claude Code CLI needs an internal mechanism that Claude can trigger programmatically:

• Something Claude can call directly from its code
• An API or internal function Claude can invoke
• A reload that happens automatically when Claude detects code changes
• NO USER INTERACTION REQUIRED

Why This is Critical:

When Claude is developing an MCP server, it should be able to:

1. Write the code
2. Save the files
3. Automatically trigger an internal MCP reload
4. Test the changes
5. Continue development

All without the user having to type anything or execute any commands.

To Be Clear:

• NOT a slash command the user types ✗
• NOT anything requiring manual intervention ✗
• YES an internal reload mechanism Claude can trigger itself ✓
• YES automatic reloading that Claude controls ✓

The solution must be something Claude Code CLI can do internally, on its own, without any user involvement. Otherwise, it defeats the entire purpose of having Claude assist with MCP development.

Thank you for your patience as we clarify this critical requirement.

Sounds like someone should build an MCP server to manage the MCP servers in CC.

But seriously, I support this issue. It's a pain because CC does a great job at helping to code the MCP well. I was able to substantially simplify an MCP server that I created that forces mildly complex git management for agents and assistants. In fact CC fixed some issues I was being lazy about.

Works well when it works, but CC doesn't want to respect the running MCP, much less reload changes without significant manual intervention.

My battle is:

• MCP servers provide tools that Claude can _choose_ to use
• They don't automatically intercept system git commands
• Claude Code has its own git integration that _doesn't automatically consult MCP servers_

I'm testing this against UI agent tools too, so I will report back if it's helpful for comparison.

How I solved that problem:

1. Thin wrapper that launches main MCP.
2. MCP has a tool "reload", which forces it to exist with special status code.
3. When wrapper detects that MCP existed with this status code relaunches it.

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.