Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Development workflow server for CrossPad — build, test, run, screenshot, and navigate code
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"crosspad": {
"command": "npx",
"args": [
"-y",
"crosspad-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add crosspad -- npx -y crosspad-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"crosspad": {
"command": "npx",
"args": [
"-y",
"crosspad-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"crosspad": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"crosspad-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CrossPad, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (4.0.1) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Whisper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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. |
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
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.
flowchart LR
core["core · always on devices · doctor · snapshot build · flash · repo status · tasks bench lease"] sim["sim PC simulator: run, screenshot, input, MIDI, settings, tests"] device["device the board over USB: console, CDC verbs, UI driving, USB mode"] hil["hil scenarios, pad stimulus, audio capture + analysis, BLE"] code["code symbols, interfaces, docs search"] git["git submodule drift, update, commit"] apps["apps crosspad-apps registry"] trace["trace 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.
GPL-3.0-or-later — see LICENSE. Part of the CrossPad project. Releases up to 10.3.0 were published under MIT.