mpc-plugin-test — Claude Code skill for MPC plugin tests
mpc-plugin-test — a Claude Code skill that tests MPC plugins in the SDK host simulator before they reach hardware. It runs after builds and helps investigate silence, noise, crashes, glitches, or lost settings.
MIT ★ 200 updated 2026-11-07
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-test -a claude-codeWhat mpc-plugin-test does
The skill runs an MPC plugin through the SDK host simulator. It inspects the plugin’s name, UID, and parameters, then checks WAV rendering, MIDI, state round trips, parameter sweeps, stability, and CPU use. The report separates failures such as crashes, invalid output, and mismatched parameters from warnings about silence, clipping, or high CPU.
The simulator cannot stand in for testing on an MPC. Its CPU reading is for the computer running the test; the MPC is 10–40 times slower, so the simulator average should stay below a few percent. For silent output, the skill points to isNoteOn, envelope handling, output gain, and writes to ctx.outputs. For clicks, it suggests checking parameter smoothing and phase resets.
Listen to the rendered WAV, then test on the MPC: copy the plugin folder to VST2 Plugins, enable Preferences → Enhancements (Beta) → External Plugin Support, load the plugin, and save and reload a project.
What it helps with
- run plugin checks after each build
- trace silent or noisy output
- catch crashes and broken state round trips
- inspect MIDI behavior and CPU use
Example prompts for the agent
- Test my MPC plugin after the build with the SDK host simulator.
- The plugin is silent; check its note handling and output.
- Find the cause of clicks and verify that plugin settings survive a reload.
How to install mpc-plugin-test
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-test -a claude-code2Manually: put the files in place
~/.claude/skills/mpc-plugin-test/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mpc-plugin-test/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-test -a codex2Manually: put the files in place
.agents/skills/mpc-plugin-test/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-test -a cursor2Manually: put the files in place
.cursor/skills/mpc-plugin-test/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inmusic-software/mpc-plugin-builder-sdk .agents/skills/mpc-plugin-test2Manually: put the files in place
.github/skills/mpc-plugin-test/SKILL.md1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-test -a gemini-cli2Platform CLI
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .agents/skills/mpc-plugin-testManually: put the files in place
.devin/skills/mpc-plugin-test/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mpc-plugin-test
How do I install mpc-plugin-test in Claude Code?
Run npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-test -a claude-code. The skill file is at ~/.claude/skills/mpc-plugin-test/SKILL.md.
What does mpc-plugin-test do?
It tests an MPC plugin with the SDK host simulator, covering WAV rendering, MIDI, state, parameters, stability, and CPU use. It also helps interpret the simulator report and investigate common audio problems.
Can the simulator replace testing on an MPC?
No. The simulator catches some crashes and DSP bugs, but the plugin still needs to be tested on an MPC.
Source text
SKILL.md · MIT
--- name: mpc-plugin-test description: Test an MPC plugin on the computer with the SDK's host simulator before putting it on hardware: load sequence, audio rendering to WAV, MIDI, state round trip, parameter sweeps, stability and CPU. Use after every build, when the user reports no sound, noise, crashes, glitches or lost settings, or asks to verify a plugin. --- # Test with the host simulator The simulator imitates the MPC's host (same load sequence, 44.1 kHz, small blocks, concurrent-looking parameter writes, the parameter-0 nudge). It cannot replace a test on the real MPC, but it catches most crashes and DSP bugs. ``` .sdk-tools/host_sim plugins/<Name>/build/native/<slug>.dylib dump # what the MPC will see: name, uid, params, kinds .sdk-tools/host_sim plugins/<Name>/build/native/<slug>.dylib test --seconds 3 --wav plugins/<Name>/build/test.wav # instruments: --notes 48,52,55 ; --playing simulates transport ; effects get a sine + noise burst # --block 32 / --block 512 for extreme block sizes ; --verbose logs every opcode ``` (On Linux the native library is `.so`, on Windows `.dll` and the simulator is `host_sim.exe`.) Read the report: - `FAIL` lines must be fixed: NaN/Inf output, crash (exit 2, with the phase named), state not round-tripping, parameter get/set mismatch. - `WARN`: silence from an instrument (no voice triggered?), clipping (reduce gain), denormals, high CPU, effect not passing silence. - Timing: the simulator reports CPU on your machine; the MPC is 10–40× slower. Keep the simulator's average under a few percent. Then listen to the WAV (ask the user to, or describe what to expect). For "no sound" problems: check `isNoteOn` handling, envelope attack/gate, output gain, and that `ctx.outputs` is written. For "clicks": smooth parameters, add short attack/release, avoid resetting phase on every block. Finally remind the user to test on the MPC itself (`docs/install-and-test.md`): copy the folder into `VST2 Plugins`, enable Preferences → Enhancements (Beta) → External Plugin Support, load it, save and reload a project.
© inmusic-software · MIT · inmusic-software/mpc-plugin-builder-sdk