MCP-Verbindung diagnostizieren

Diagnose and resolve MCP server connection failures.

Wann verwenden

• Claude Code or Claude Desktop fails to connect to an MCP server
• MCP tools don't appear in sessions
• "Cannot attach der Server" errors
• Connection was working but stopped
• Setting up MCP on a new machine

Eingaben

• Erforderlich: Error message or symptom description
• Erforderlich: Which client (Claude Code, Claude Desktop, or both)
• Erforderlich: Which MCP server (mcptools, Hugging Face, custom)
• Optional: Recent changes to configuration or environment

Vorgehensweise

Schritt 1: Identifizieren the Client and Configuration

Claude Code (WSL):

# View MCP configuration
claude mcp list
claude mcp get server-name

# Configuration stored in
cat ~/.claude.json | python3 -m json.tool

Claude Desktop (Windows):

# Configuration file location
cat "/mnt/c/Users/$USER/AppData/Roaming/Claude/claude_desktop_config.json"

Erwartet: Configuration file is located and readable, showing the MCP server entries with command, args, and env fields.

Bei Fehler: If the config file nicht exist or is empty, der Server was never configured. Follow the

configure-mcp-server

skill to set it up from scratch.

Schritt 2: Testen Server Independently

R mcptools:

# Test if R can start the server
"/mnt/c/Program Files/R/R-4.5.0/bin/Rscript.exe" -e "mcptools::mcp_server()"

If this fails:

• Check R path exists:

  ls "/mnt/c/Program Files/R/"

• Check mcptools is installed:

  Rscript -e "library(mcptools)"

• Check ellmer Abhaengigkeit:

  Rscript -e "library(ellmer)"

Hugging Face MCP:

# Test mcp-remote directly
mcp-remote https://huggingface.co/mcp

# Check if mcp-remote is installed
which mcp-remote
npm list -g mcp-remote

Erwartet: The server process starts and produces initialization output (JSON-RPC handshake or "listening" message) ohne errors.

Bei Fehler: If R mcptools fails, check that the R version path is correct and that mcptools is installed in the R library. If mcp-remote fails, reinstall globally with

npm install -g mcp-remote

and verify it is on the PATH.

Schritt 3: Diagnose Common Error Patterns

"Cannot attach der Server" (Claude Desktop)

Root cause: Windows command argument parsing.

Fix: Use Umgebungsvariables stattdessen of

--header

arguments:

{
  "hf-mcp-server": {
    "command": "mcp-remote",
    "args": ["https://huggingface.co/mcp"],
    "env": { "HF_TOKEN": "your_token" }
  }
}

Also ensure

mcp-remote

is globally installed (

npm install -g mcp-remote

), not relying on

npx

.

"Connection refused"

• Server isn't running or port is wrong
• Firewall blocking the connection
• Wrong transport type (stdio vs HTTP)

"Command not found"

• Missing full path to executable
• PATH not configured in the execution context
• On Windows: use

  C:\\PROGRA~1\\...

  for paths with spaces

MCP tools don't appear but no error

• Server starts but tools aren't registered
• Check server stdout for initialization messages
• Verifizieren der Server uses the correct MCP protocol version

Erwartet: Error pattern matched to one of the documented categories (cannot attach, connection refused, command not found, or silent failure).

Bei Fehler: If der Fehler nicht match any known pattern, capture the full error output and check server-side logs. Suchen for the exact Fehlermeldung in the MCP server's GitHub issues.

Schritt 4: Check Network and Authentication

# Test Hugging Face API connectivity
curl -I "https://huggingface.co/mcp"

# Verify token validity
curl -H "Authorization: Bearer $HF_TOKEN" https://huggingface.co/api/whoami

Erwartet: HTTP endpoint returns 200 status and the whoami call returns your Hugging Face username, confirming network connectivity and valid Authentifizierung.

Bei Fehler: If curl returns a connection error, check DNS resolution and proxy settings. If the token is rejected (401), regenerate the token at huggingface.co/settings/tokens and update die Konfiguration.

Schritt 5: Verifizieren JSON Configuration Syntax

# Validate JSON (common issue: trailing commas, missing quotes)
python3 -m json.tool /path/to/config.json

Erwartet: JSON parses ohne errors, confirming die Konfiguration file has valid syntax.

Bei Fehler: The most common JSON issues are trailing commas nach the last entry in an object or array, missing quotes around string values, and mismatched braces. Beheben the syntax error reported by the parser and re-validate.

Schritt 6: Platform-Specific Debugging

Windows (Claude Desktop):

• Argument parsing differs from Unix
• Spaces in paths break command execution
• Use 8.3 short paths:

  C:\PROGRA~1\R\R-45~1.0\bin\x64\Rscript.exe

• Environment variables work more reliably than command-line headers

WSL (Claude Code):

• Unix-style quoting works korrekt
• Can use full paths with spaces (quoted)
• npm/npx via NVM: ensure NVM is loaded in the execution context

Erwartet: Platform-specific issue identified (e.g., Windows argument parsing, WSL path resolution, or NVM context loading).

Bei Fehler: If das Problem is Windows-specific, switch from command-line arguments to Umgebungsvariables for Authentifizierung. If WSL-specific, verify that the Windows executable path is accessible from WSL using the full

/mnt/c/...

path.

Schritt 7: Zuruecksetzen and Reconfigure

If all else fails:

# Remove and re-add the server (Claude Code)
claude mcp remove server-name
claude mcp add server-name stdio "/full/path/to/executable" -- args

# Restart Claude Desktop after config changes
# (close and reopen the application)

Erwartet: After removing and re-adding der Server,

claude mcp list

shows der Server with the correct configuration and a fresh connection attempt succeeds.

Bei Fehler: If re-adding fails, check that the executable path is correct and the command works when run directly in the terminal. For Claude Desktop, ensure die Anwendung is fully closed (check system tray) vor restarting.

Schritt 8: Check Logs

Claude Code: Look for MCP errors in the terminal output when starting a session.

Claude Desktop: Check application logs (location varies by OS).

Server-side: Hinzufuegen logging to the MCP server to capture incoming requests and errors.

Erwartet: Log entries reveal the specific point of failure (server startup, handshake, Authentifizierung, or tool registration).

Bei Fehler: If no logs are available, add

stderr

capture to der Server command (e.g., redirect to a log file) and reproduce the failure. For Claude Desktop, check

%APPDATA%\Claude\logs\

for application-level logs.

Validierung

• Server starts independently ohne errors
• Configuration JSON is valid
• Client connects erfolgreich
• MCP tools appear in the session
• Tools execute korrekt when called
• Connection persists across multiple requests

Haeufige Stolperfallen

• Editing the wrong config file: Claude Code (

  ~/.claude.json

  ) vs Claude Desktop (

  %APPDATA%\Claude\claude_desktop_config.json

  )
• Not restarting nach config changes: Claude Desktop requires restart; Claude Code picks up changes on new session
• npx in restricted environments: npx downloads packages at runtime. If network or Berechtigungs are restricted, install globally.
• Token expiration: Hugging Face tokens can expire. Regenerate if auth failures appear suddenly.
• Version mismatches: MCP protocol versions muss compatible zwischen client and server

Verwandte Skills

• configure-mcp-server

  - initial MCP setup

• build-custom-mcp-server

  - custom server debugging context

• setup-wsl-dev-environment

  - WSL prerequisite setup