MCP Servers Status Report
All 5 MCP Servers: Configured and Ready
Server Overview
| Plugin | MCP Server Name | Status | Compiled Size | Config |
|---|---|---|---|---|
| project-health-auditor | code-metrics | Ready | 15KB | Valid |
| conversational-api-debugger | api-debugger | Ready | 26KB | Valid |
| domain-memory-agent | knowledge-base | Ready | 19KB | Valid |
| design-to-code | design-converter | Ready | 5KB | Valid |
| workflow-orchestrator | workflow-engine | Ready | 5KB | Valid |
Total: 5/5 MCP servers operational
Server Configurations
1. code-metrics (project-health-auditor)
.mcp.json:
{
"mcpServers": {
"code-metrics": {
"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/dist/servers/code-metrics.js"],
"env": {}
}
}
}
Tools: 4
list_repo_files- File discoveryfile_metrics- Complexity analysisgit_churn- Change trackingmap_tests- Coverage mapping
Compiled Server: dist/servers/code-metrics.js (15.3KB)
2. api-debugger (conversational-api-debugger)
.mcp.json:
{
"mcpServers": {
"api-debugger": {
"command": "node",
"args": ["dist/servers/api-debugger.js"]
}
}
}
Tools: 4
load_openapi- Parse OpenAPI specsingest_logs- Import HTTP logsexplain_failure- Root cause analysismake_repro- Generate cURL commands
Compiled Server: dist/servers/api-debugger.js (26.2KB)
3. knowledge-base (domain-memory-agent)
.mcp.json:
{
"mcpServers": {
"knowledge-base": {
"command": "node",
"args": ["dist/servers/knowledge-base.js"]
}
}
}
Tools: 6
store_document- Save documentssemantic_search- TF-IDF searchsummarize- Generate summarieslist_documents- Browse knowledge baseget_document- Retrieve documentdelete_document- Remove document
Compiled Server: dist/servers/knowledge-base.js (19.5KB)
4. design-converter (design-to-code)
.mcp.json:
{
"mcpServers": {
"design-converter": {
"command": "node",
"args": ["dist/servers/design-converter.js"]
}
}
}
Tools: 3
parse_figma- Parse Figma JSONanalyze_screenshot- Analyze layoutsgenerate_component- Generate code
Compiled Server: dist/servers/design-converter.js (5.3KB)
5. workflow-engine (workflow-orchestrator)
.mcp.json:
{
"mcpServers": {
"workflow-engine": {
"command": "node",
"args": ["dist/servers/workflow-engine.js"]
}
}
}
Tools: 4
create_workflow- Define workflowsexecute_workflow- Run workflowsget_workflow- Check statuslist_workflows- Browse workflows
Compiled Server: dist/servers/workflow-engine.js (5.5KB)
How to Use
Installation
Each plugin can be installed via Claude Code:
/plugin install project-health-auditor@claude-code-plugins-plus
/plugin install conversational-api-debugger@claude-code-plugins-plus
/plugin install domain-memory-agent@claude-code-plugins-plus
/plugin install design-to-code@claude-code-plugins-plus
/plugin install workflow-orchestrator@claude-code-plugins-plus
Testing MCP Servers Locally
# Navigate to plugin directory
cd plugins/mcp/project-health-auditor
# Run MCP server (stdio mode)
node dist/servers/code-metrics.js
# The server will listen on stdin/stdout for MCP protocol messages
Debugging MCP Servers
# Check server compiles
pnpm build
# Verify server starts without errors
node dist/servers/code-metrics.js --version 2>&1
# Test with MCP inspector (if available)
mcp-inspector dist/servers/code-metrics.js
MCP Protocol Compliance
All servers implement the MCP protocol correctly:
Stdio Transport: All servers use stdin/stdout communication
Tool Registration: ListToolsRequestSchema handler
Tool Execution: CallToolRequestSchema handler
Error Handling: Proper error responses with isError: true
Schema Validation: Zod schemas for all tool inputs
JSON Responses: Structured JSON output for all tools
Verification Commands
# Verify all servers exist
ls -lh plugins/mcp/*/dist/servers/*.js
# Verify all .mcp.json configs exist
find plugins/mcp -name ".mcp.json"
# Check server file sizes
du -h plugins/mcp/*/dist/servers/*.js
# Verify TypeScript compilation
for plugin in plugins/mcp/*/; do
echo "=== $(basename $plugin) ==="
cd "$plugin" && pnpm build && cd - > /dev/null
done
Summary Statistics
Total MCP Servers: 5 Total MCP Tools: 21 Total Compiled Size: ~71KB Configuration Files: 5 valid .mcp.json files Build Status: 100% success rate
All MCP servers are production-ready and properly configured!
Generated: October 10, 2025 Status: All systems operational