MCP connections should support dynamic reconnection

Resolved 💬 3 comments Opened Jan 15, 2026 by MauveAvenger Closed Jan 19, 2026

Problem

When an MCP server becomes available after a Claude Code session has started, the connection fails with:

Server not initialized

The only workaround is to exit Claude Code and start a new session with the MCP server already running.

Example Scenario

  1. Start Claude Code (MCP server not running)
  2. Later, start the MCP server (e.g., Blockbench with MCP plugin)
  3. Try to use MCP tools → fails with "Server not initialized"
  4. Must exit and restart Claude Code for connection to work

Expected Behavior

Claude Code should:

  • Detect when an MCP server becomes available
  • Automatically initialize/reconnect to the MCP server
  • Allow MCP tools to work without requiring a session restart

Current Workaround

User must ensure all MCP servers are running before starting Claude Code, which is cumbersome for desktop applications like Blockbench that aren't always-on services.

Environment

  • Claude Code CLI
  • MCP server type: HTTP (http://localhost:3000/bb-mcp)
  • Server: Blockbench with MCP Server plugin

View original on GitHub ↗

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