The MCP server provides Claude Code with control over the CrossPad development workflow, enabling users to build, test, manage app packages, interact with a simulator, and search code across repositories using natural language.
From the registry: Development workflow server for CrossPad — build, test, run, screenshot, and navigate code
Please install the `crosspad-mcp` MCP server into my current AI client (that's you).
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","crosspad-mcp-server"]
- optional environment variables:
- `CROSSPAD_IDF_ROOT`: Path to platform-idf repo. (example: `/path/to/platform-idf`)
- `CROSSPAD_PC_ROOT`: Path to crosspad-pc repo. (example: `/path/to/crosspad-pc`)
- `CROSSPAD_GIT_DIR`: Base directory for repo discovery (flat layout). (example: `~/GIT`)
- `CROSSPAD_ARDUINO_ROOT`: Path to Arduino ESP32-S3 repo.
- `CROSSPAD_CORE_ROOT`: Path to crosspad-core repo.
- `CROSSPAD_GUI_ROOT`: Path to crosspad-gui repo.
- `IDF_PATH`: ESP-IDF SDK path (auto-detected). (example: `~/esp/esp-idf`)
- `VCPKG_ROOT`: vcpkg installation path. (example: `~/vcpkg`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CROSSPAD_IDF_ROOTrequiredPath to the ESP-IDF platform repo.CROSSPAD_PC_ROOTrequiredPath to the PC simulator repo.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.