kicad-mcp requires the pcbnew Python module which is only available with a KiCAD installation. The container builds successfully but fails validation because pcbnew cannot be pip-installed or included in the container. - Added "Host-Only MCP Servers" section to STATUS.md - Updated detailed status table with kicad-mcp entry - Added JOURNAL.md entry documenting the finding - Updated docker-compose.yml to use custom Dockerfile This MCP can only be used on a host machine with KiCAD installed. It cannot be integrated into Crush via Docker. Build details: - Container size: 463MB - Base: node:22-alpine with Python 3 + pip - Dependencies: kicad-skip, Pillow, cairosvg, colorlog, pydantic Validation error: [ERROR] pcbnew validation failed: ModuleNotFoundError: No module named 'pcbnew' Root cause: - KiCAD's pcbnew is a C++ Python binding bundled with KiCAD - Cannot be installed via pip or any package manager - Server validates pcbnew at startup and exits if missing Pattern identified: Some MCPs integrate with desktop applications and cannot be containerized. These should be documented as host-only and excluded from Docker-based Crush integration. Next MCP to process: matomo-mcp 💘 Generated with Crush Assisted-by: GLM-5 via Crush <crush@charm.land>
14 KiB
14 KiB