skills.rest
photonics-dhl
photonics-dhlCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

claude-code-mcp-debugging

Diagnose MCP servers reporting Connected but exposing no tools.

Updated Apr 30, 2026
Search Tags:#debugging#claude#mcp#tools#health-check#minimax
One-click install
npx skills add https://github.com/photonics-dhl/Hermes --skill claude-code-mcp-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-code-mcp-debugging
Source: https://github.com/photonics-dhl/Hermes/tree/main/hermes-home/skills/dev-helper/claude-code-mcp-debugging
Command: npx skills add https://github.com/photonics-dhl/Hermes --skill claude-code-mcp-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps identify and resolve situations where Claude MCP servers show "Connected" in health checks but fail to expose tools in conversations, enabling reliable tool access during chats.

Core Features & Use Cases

  • Layered diagnostic approach across server health, MCP protocol, and conversational tool exposure.
  • Actionable remediation steps for common misconfigurations and permission gaps.
  • Use Case: When Claude Code MCP reports connectivity but no tools appear, run this guide to surface root causes and fixes.

Quick Start

Follow the diagnostic steps to verify health, protocol, and conversation exposure for your Claude Code MCP server.

Frequently Asked Questions about claude-code-mcp-debugging

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

FAQPage Schema
Why does my Claude MCP server show Connected but no tools appear in conversations?▼

Claude MCP servers can show Connected in health checks but fail to expose tools in conversations due to misconfigurations or permission gaps. This diagnostic guide applies Layer 1 health checks, Layer 2 protocol tests, and Layer 3 conversation verification to pinpoint the exact failure point.

How do I troubleshoot tool exposure failures in a uvx-based MiniMax MCP implementation?▼

To troubleshoot uvx-based MiniMax MCP implementations, apply layered diagnostic steps to verify server health, inspect MCP protocol responses, and validate conversation tool exposure. This process surfaces root causes and provides actionable remediation steps for common configuration issues.

What is the best way to diagnose MCP protocol responses when health checks pass but tools are missing?▼

The best way to diagnose MCP protocol responses is to enforce a layered diagnostic approach that tests server health, protocol behavior, and conversational tool exposure. This method identifies underlying permission gaps or misconfigurations that prevent tool visibility.

Can I use this diagnostic guide to fix permission gaps in Claude Code MCP servers?▼

Yes, you can use this guide to fix permission gaps in Claude Code MCP servers. It provides actionable remediation steps for common misconfigurations and verifies tool exposure under common failure modes to ensure reliable tool access during chats.

Does this MCP debugging approach work for all Claude Code servers or only uvx-based MiniMax implementations?▼

This debugging approach applies specifically to Claude Code MCP servers, focusing on uvx-based MiniMax implementations. It diagnoses health status, protocol responses, and tool exposure to resolve connectivity issues where tools fail to appear.

Related Skills

Explore More Software Engineering Skills→
evolv3-aievolv3-ai
1

admin-mcp

Install and configure MCP servers for Claude Desktop on Windows and WSL contexts.

Official
Advanced
PosteriotPosteriot

security-auditor

Audit Makalah app auth, permissions, APIs, webhooks, and data exposure.

Community
Advanced
rwxprojectrwxproject

mcp-tester

Test MCP server connectivity and tool execution across stdio, http, and sse transports.

Community
Advanced
youdotcom-ossyoudotcom-oss
25

mcp-patterns

Standardize MCP server tooling with schemas, logging, and error handling patterns.

Official
Intermediate