lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Debug MCP Integration
Add to your project's CLAUDE.md:
MCP Server Debugging (debug-mcp)
This project uses the debug-mcp plugin for diagnosing and developing MCP server integrations.
Available Commands
| Command | Description |
|---|---|
/debug-mcp status |
Show health status of all configured MCP servers |
/debug-mcp test |
Test a specific MCP tool call with parameters |
/debug-mcp logs |
View and analyze recent MCP server error logs |
/debug-mcp inspect |
Deep inspection of server config, dependencies, and tools |
/debug-mcp scaffold |
Generate a new MCP server project skeleton |
Usage Guidelines
- Run
/debug-mcp statuswhen Claude Code reports MCP server failures at session start - Use
/debug-mcp inspect <server> --depsto diagnose missing package issues - Use
/debug-mcp test <server> <tool>to verify individual tool functionality - Use
/debug-mcp logs --errors-onlyto quickly find error patterns - Use
/debug-mcp scaffoldwhen creating a new MCP server integration
Common Troubleshooting
| Symptom | Command |
|---|---|
| "X MCP servers failed" at startup | /debug-mcp status |
| Tool call returns error | /debug-mcp test <server> <tool> |
| ImportError in server | /debug-mcp inspect <server> --deps |
| Unknown server errors | /debug-mcp logs --server=<name> |