mcp-troubleshooting

Diagnose MCP server connection failures in Claude Desktop.

Updated Aug 27, 2024
One-click install
npx skills add https://github.com/rhayalcantara/evaluacionesEmpleadosdocker --skill mcp-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-troubleshooting
Source: https://github.com/rhayalcantara/evaluacionesEmpleadosdocker/tree/main/.claude/skills/mcp-problems
Command: npx skills add https://github.com/rhayalcantara/evaluacionesEmpleadosdocker --skill mcp-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and often frustrating process of diagnosing and resolving common issues with Model Context Protocol (MCP) servers in Claude Desktop. It helps you quickly identify why your MCP servers are disconnecting, failing to initialize, or encountering handshake problems, ensuring your AI agents can access necessary external tools and data without interruption.

Core Features & Use Cases

  • Automated Log Analysis: Guides you through extracting and interpreting Claude Desktop and MCP server logs to pinpoint the root cause of connection failures.
  • Common Problem Solutions: Provides step-by-step fixes for issues like missing Python modules, incomplete handshakes, premature server termination, and incorrect stdout/stderr usage.
  • Cross-Platform Support: Covers troubleshooting for Python (MySQL, SQL Server, PostgreSQL) and Node.js MCP servers across Windows, macOS, and Linux environments.
  • Use Case: Your Claude Desktop shows "Server disconnected" for your 'mysql-local' MCP server. Use this skill to automatically check the logs, identify a ModuleNotFoundError, and guide you to install the correct Python dependency, getting your database context back online without manual guesswork or extensive research.

Quick Start

My MCP server 'mysql-local' is showing "Server disconnected". Help me troubleshoot it.

Frequently Asked Questions about mcp-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why my MCP server is showing 'Server disconnected' in Claude Desktop?

MCP server disconnections stem from handshake failures, missing dependencies, or logging misconfiguration. Extract logs from Claude Desktop and your MCP server, check for ModuleNotFoundError or premature termination, verify stdout/stderr aren't used for protocol output, and confirm the server implements initialize, resources/list, and tools/list handlers.

What causes MCP server connection failures on Windows, macOS, and Linux?

Connection failures across platforms commonly result from missing Python modules (MySQL, SQL Server, PostgreSQL drivers), incomplete MCP protocol handshakes, incorrect environment setup, non-stdout logging interfering with protocol output, or Node.js/Python runtime misconfigurations. Cross-platform troubleshooting requires examining platform-specific log locations and dependency resolution.

Can I troubleshoot Python-based MCP servers for MySQL, SQL Server, and PostgreSQL?

Yes. Python MCP servers for MySQL, SQL Server, and PostgreSQL can be diagnosed by checking log output for import errors, validating MCP protocol compliance (initialize, resources/list, tools/list responses), confirming non-stdout logging, and verifying database driver installation and configuration on your platform.

How do I fix a Python MCP server that fails to initialize or complete handshakes?

Initialization and handshake failures require extracting Claude Desktop logs, identifying the exact error point in protocol exchange, verifying all required MCP handlers are implemented, checking that logs don't write to stdout, ensuring dependencies are installed, and validating configuration syntax matches your platform's requirements.

What should I check if my Node.js MCP server disconnects unexpectedly?

For Node.js MCP servers, verify the process doesn't terminate prematurely, logs route to files rather than stdout, all MCP protocol functions (initialize, resources/list, tools/list) return properly formatted responses, dependencies resolve correctly, and Claude Desktop logs show the exact disconnect point for root-cause isolation.

Do I need to manually parse server logs to troubleshoot MCP connection issues?

Log parsing guidance automates root-cause isolation: extract Claude Desktop and MCP server logs, scan for ModuleNotFoundError, handshake timeouts, or unexpected termination, cross-reference protocol compliance requirements, and apply targeted fixes based on error patterns rather than manual guesswork.