Troubleshooting
Server setup issues
Section titled “Server setup issues”Server not starting
Section titled “Server not starting”ModuleNotFoundError: No module named 'mcp'
Dependencies are not installed. Run:
make installSyntax errors or unsupported features
Verify you are using Python 3.10 or higher:
python --versionFileNotFoundError or path-related errors
Check your .env file and ensure all configured paths exist. See Environment Variables for the full list.
PermissionError: [Errno 13] Permission denied
Ensure you have read/write permissions for all configured directories and files.
MCP client integration
Section titled “MCP client integration”Server not appearing in Claude Desktop
Section titled “Server not appearing in Claude Desktop”Check the configuration file:
macOS:
cat ~/Library/Application\ Support/Claude/claude_desktop_config.jsonWindows:
type %APPDATA%\Claude\claude_desktop_config.jsonEnsure it contains:
{ "mcpServers": { "kicad": { "command": "/ABSOLUTE/PATH/TO/kicad-mcp/.venv/bin/python", "args": [ "/ABSOLUTE/PATH/TO/kicad-mcp/main.py" ] } }}Always use absolute paths. Replace:
"args": ["main.py"]with:
"args": ["/absolute/path/to/main.py"]Restart Claude Desktop after editing the configuration.
Protocol version mismatch — update both the client and server to compatible versions.
KiCad integration
Section titled “KiCad integration”KiCad Python modules not found
Section titled “KiCad Python modules not found”Warning messages about missing KiCad Python modules indicate limited functionality for some features. Solutions:
- Install KiCad from kicad.org
- Set
KICAD_APP_PATHfor non-standard installations - Check server logs for Python path setup errors
Unable to open projects
Section titled “Unable to open projects”- Verify KiCad is installed and
KICAD_APP_PATHis correct - Double-check the project file path (use absolute paths)
- Ensure the file has a
.kicad_proextension - Check file and application permissions
Project discovery
Section titled “Project discovery”Projects not found
Section titled “Projects not found”- Configure search paths in
.env:KICAD_SEARCH_PATHS=~/pcb,~/Electronics,~/Projects/KiCad - Set
KICAD_USER_DIRif using a custom directory:KICAD_USER_DIR=~/Documents/KiCadProjects - Ensure projects have the
.kicad_proextension - Restart the server after configuration changes
DRC and export issues
Section titled “DRC and export issues”DRC checks failing
Section titled “DRC checks failing”- Ensure your project contains a
.kicad_pcbfile - Verify
kicad-cliis available:Or setTerminal window which kicad-cliKICAD_CLI_PATHin.env - Verify the PCB file can be opened in KiCad
Export tools failing
Section titled “Export tools failing”- Check
kicad-cliavailability (same as DRC) - Verify the source file exists and is valid
- Check write permissions in the output directory
PCB thumbnail/SVG generation failing
Section titled “PCB thumbnail/SVG generation failing”- Ensure the project has a valid
.kicad_pcbfile - Check that
kicad-clisupports SVG export (KiCad 9+) - Use absolute file paths
Logging and debugging
Section titled “Logging and debugging”Checking logs
Section titled “Checking logs”mckicad writes logs to mckicad.log in the project root, overwritten on each start.
For Claude Desktop logs:
macOS:
tail -n 20 -F ~/Library/Logs/Claude/mcp-server-kicad.logtail -n 20 -F ~/Library/Logs/Claude/mcp.logWindows: check %APPDATA%\Claude\Logs\
Using the MCP Inspector
Section titled “Using the MCP Inspector”For interactive debugging, use the MCP Inspector:
npx @modelcontextprotocol/inspector uv --directory . run main.pyThis lets you call tools directly and inspect responses without going through an AI client.
Platform-specific issues
Section titled “Platform-specific issues”Permission denied accessing files — ensure Terminal has full disk access in System Preferences > Security & Privacy.
System Python vs Homebrew Python — specify the full path to the Python interpreter in your client configuration. Use the .venv/bin/python from make install.
Windows
Section titled “Windows”Path separator issues — use forward slashes (/) in all paths, or double backslashes (\\).
Cannot launch KiCad — ensure KICAD_APP_PATH is set correctly in .env.
Non-standard KiCad location — set KICAD_APP_PATH to your installation path.
Permission issues — check file permissions with ls -la and adjust with chmod if needed.
Still having issues?
Section titled “Still having issues?”- Use the MCP Inspector for direct tool testing
- Check
mckicad.logfor detailed error information - Set
LOG_LEVEL=DEBUGin.envfor verbose logging - Open an issue with:
- Clear description of the problem
- Steps to reproduce
- Error messages or log excerpts
- Environment details (OS, Python version, KiCad version)