Crosspad Mcp

io.github.CrossPad由 GitHub 账号 CrossPad 发布v4.0.1更新于 Oct 24, 2026

Development workflow server for CrossPad — build, test, run, screenshot, and navigate code

已验证STDIO仅桌面开发者工具AI 与机器学习

概览

AI 生成的概览

本地 MCP 服务器，让助手通过 ESP-IDF 与 STM32 工具链构建、烧录、模拟、测试并诊断 CrossPad 打击垫控制器的固件。

可以做什么
构建、烧录并安装固件与应用，包括 OTA 上传和从 crosspad-apps 注册表安装子模块，长操作以可查询的任务运行。运行 PC 模拟器，截取 LCD 画面，发送打击垫与编码器输入，并操作 MIDI 与设置。通过 USB 操作开发板：控制台、CDC 命令、界面驱动、USB 模式与设备检查。运行硬件在环场景、打击垫激励、USB 音频采集与分析以及 BLE 测试。诊断崩溃，并通过 ST-Link 在不暂停内核的情况下实时跟踪 STM32 变量。在整个生态中查找符号、接口实现与文档，并检查子模块漂移与提交。
适用场景
适合开发 CrossPad 固件或应用、希望让助手代为执行构建、烧录、模拟器会话、硬件在环测试和崩溃诊断的人。也适合在多个仓库间浏览 CrossPad 代码库。
运行要求
通过 npx 以 crosspad-mcp-server npm 包在本地以 stdio 运行，仅限桌面。需要 CrossPad 工具链（ESP-IDF、STM32/ST-Link、clangd），硬件相关工具还需连接开发板。除非配置路径，否则假定各仓库并列位于 ~/GIT/ 下。未声明 API 密钥或环境变量。
安装前请注意
工具会写入设备和主机：烧录、DFU 与 SWD 写入会先要求确认，只读模式会移除所有写入类工具。构建、烧录和场景会改动固件与仓库，应用安装会添加子模块。硬件工具需要实际连接的开发板。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Crosspad Mcp，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

crosspad-mcp

[npm] [M8ven Live Monitored] [CI] [node] [license: GPL-3.0-or-later]

Talk to your CrossPad. Let Claude do the toolchain.

crosspad-mcp is an MCP server that teaches Claude Code (or any MCP client) how to develop for the CrossPad pad controller. You say "flash the new build and check that it boots"; it runs the ESP-IDF build, asks you to confirm the flash, opens the console, runs the smoke scenario and tells you what happened — with the hardware traps already built in, so you don't have to remember which serial port reboots the board when you open it.

[You prompt Claude Code, Claude Code talks MCP to crosspad-mcp, crosspad-mcp drives the PC simulator over TCP, the CrossPad board over USB and the STM32 co-processor over ST-Link]

What you can do with it

Every card is a real prompt. The tools named underneath are what runs — you never have to call them yourself.

Say this……and this happens
"Build the firmware and flash it over OTA."crosspad_build platform=idf streams the build, crosspad_flash transport=ota asks for confirmation, then streams the upload. New app directories are detected and the fullclean is done for you.
"Show me what's on the simulator screen."crosspad_run launches the PC sim, crosspad_screenshot returns the LCD as an image Claude can actually look at. Then "press pad 5", "turn the encoder left twice" — crosspad_input.
"Play a drum pattern on the pads and record what comes out."crosspad_stimulus hits the pads with real timings, crosspad_capture records the board through its own USB-audio endpoint, crosspad_analyze gives a verdict (onsets, clicks, silence, velocity curve).
"Why did it crash?"crosspad_diagnose_crash — reset reason, registers, backtrace decoded against the ELF that is actually flashed, heap after restart. One call.
"Watch the battery charger state machine while I plug the cable in."crosspad_trace polls STM32 variables live over ST-Link without halting the core, and plots them.
"Install the sampler app and rebuild."crosspad_apps_install app_name=sampler adds the submodule from the crosspad-apps registry, then a clean build.
"Where is IPadLogicHandler implemented?"crosspad_interface_implementations across every repo of the ecosystem, or crosspad_symbol for clangd-precise definitions and call hierarchies.
"Is my board even connected?"crosspad_devices and crosspad_doctor — which USB mode it is in, which ports belong to it, what is missing on the host, and how to fix each thing.

Quick start

bash
claude mcp add crosspad -- npx -y crosspad-mcp-server

Restart Claude Code, then ask:

is my CrossPad connected, and is the toolchain set up?

That runs crosspad_doctor. Every failed check comes with a fix. The server assumes your repos live side by side under ~/GIT/ — if they don't, set the paths once.

Installing the bundled crosspad skill gives Claude the ecosystem map, the per-role guides and the hardware traps up front:

/plugin marketplace add CrossPad/crosspad-mcp/plugin install crosspad@crosspad

How it is organised

Only the core toolset is visible when the server starts, so the tool list stays small. Claude enables the others as the conversation needs them — or you start the server with --toolsets device,sim.

mermaid
flowchart LR    core["core · always on<br/>devices · doctor · snapshot<br/>build · flash · repo status · tasks<br/>bench lease"]    sim["sim<br/>PC simulator: run, screenshot,<br/>input, MIDI, settings, tests"]    device["device<br/>the board over USB: console,<br/>CDC verbs, UI driving, USB mode"]    hil["hil<br/>scenarios, pad stimulus,<br/>audio capture + analysis, BLE"]    code["code<br/>symbols, interfaces,<br/>docs search"]    git["git<br/>submodule drift,<br/>update, commit"]    apps["apps<br/>crosspad-apps registry"]    trace["trace<br/>SWD live variables"]    core --> sim & device & code & git & apps    device --> hil    core --> trace

Anything that writes to a device or your host is tiered. Flashing, DFU and SWD writes come back as confirmation required first; --read-only removes every writing tool from the list entirely. Long operations (builds, flashes, scenarios) run as tasks you can check on, wait for or cancel.

Who is it for

Going deeper

  • Usage reference — every install path, every tool and toolset, resources and prompts, configuration, HTTP transport, the v10 migration table.
  • FAQ — the questions that cost people an afternoon.
  • CHANGELOG

License

GPL-3.0-or-later — see LICENSE. Part of the CrossPad project. Releases up to 10.3.0 were published under MIT.

来源：README.md，提交 50e2263

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v4.0.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分