MCP status display shows 'Failed to reconnect' but MCP actually works fine

Resolved 💬 2 comments Opened Jun 22, 2026 by hyunwooklee-musinsa Closed Jun 25, 2026

Description

The /mcp command shows Failed to reconnect to atlassian status, but the Atlassian MCP server is actually working perfectly.

Steps to Reproduce

  1. Run /mcp command in Claude Code
  2. Output shows: Failed to reconnect to atlassian.
  3. However, Atlassian MCP tools work correctly (tested with atlassianUserInfo - successfully returned user data)

Expected Behavior

The MCP status display should accurately reflect whether the MCP server is actually functional, not just whether the initial connection/reconnection succeeded.

Actual Behavior

  • Status shows: Failed
  • Actual functionality: Working correctly

Environment

  • Claude Code version: 2.1.42
  • OS: macOS (Darwin 25.4.0)
  • MCP Server: Atlassian (HTTP type)

Impact

This creates confusion as users think the MCP is broken when it's actually working fine.

Suggested Fix

The status check should verify actual functionality (e.g., make a simple API call) rather than just connection status.

View original on GitHub ↗

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