mpc-plugin-build — Claude Code skill for MPC plugin builds
The mpc-plugin-build Claude Code skill builds MPC plugin projects into deployable folders and helps resolve build failures. It activates when a plugin needs compiling or a build reports errors.
MIT ★ 200 updated 2026-11-07
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a claude-codeWhat mpc-plugin-build does
The skill builds an MPC plugin with python tools/build.py plugins/<Name>, producing native, ARM32 and ARM64 outputs along with skins and validation files. A native target runs a focused compile check; --target desktop creates a VST2 build for the current computer.
It diagnoses compiler and linker messages, validator failures, and crashes during host_sim loading. Linking supports only the C and C++ standard libraries; third-party DSP sources must be placed in src/. The first build may download Zig into .sdk-tools/. If Zig is needed without network access, install it separately and add it to PATH or set ZIG=. Installed GCC cross-compilers and the Docker toolchain are also supported.
What it helps with
- build an MPC plugin for native, ARM32 and ARM64
- run a focused compile check for
native - trace compiler or linker failures
- diagnose validator errors or a
host_simcrash - create a desktop VST2 build
Example prompts for the agent
- Build the MPC plugin in
plugins/<Name>and fix any build errors. - Run a quick
nativebuild check forplugins/<Name>. - Build a desktop VST2 from
plugins/<Name>.
How to install mpc-plugin-build
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a claude-code2Manually: put the files in place
~/.claude/skills/mpc-plugin-build/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mpc-plugin-build/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a codex2Manually: put the files in place
.agents/skills/mpc-plugin-build/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a cursor2Manually: put the files in place
.cursor/skills/mpc-plugin-build/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inmusic-software/mpc-plugin-builder-sdk .agents/skills/mpc-plugin-build2Manually: put the files in place
.github/skills/mpc-plugin-build/SKILL.md1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a gemini-cli2Platform CLI
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .agents/skills/mpc-plugin-buildManually: put the files in place
.devin/skills/mpc-plugin-build/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-build
How do I install mpc-plugin-build in Claude Code?
Run npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a claude-code. The skill file is placed at ~/.claude/skills/mpc-plugin-build/SKILL.md.
What does mpc-plugin-build do?
It builds MPC plugin projects for native, ARM32 and ARM64 targets, and helps diagnose compiler, linker, validator, and host_sim loading failures.
What is needed to build an MPC plugin?
The first run may download Zig into .sdk-tools/. Alternatively, use installed arm-linux-gnueabihf-g++ and aarch64-linux-gnu-g++ cross-compilers or the Docker toolchain. Linking supports only the C and C++ standard libraries.
Source text
SKILL.md · MIT
---
name: mpc-plugin-build
description: Build an MPC plugin project into the deployable "<Manufacturer> - VST - <Name>" folder (native + 32-bit ARM + 64-bit ARM), and fix compiler, linker, toolchain and validation errors. Use whenever a plugin needs compiling or a build fails.
---
# Build
```
python tools/build.py plugins/<Name> # everything: native, arm32, arm64, skins, version.xml, validate
python tools/build.py plugins/<Name> --target native # quick compile check + params.json + skins
python tools/build.py plugins/<Name> --debug # -O0 -g for the native build when debugging
```
The first run may install the Zig cross compiler into `.sdk-tools/` (one-time download). `--toolchain gcc` uses installed `arm-linux-gnueabihf-g++` / `aarch64-linux-gnu-g++`; `--toolchain docker` uses `tools/docker/Dockerfile`.
Output: `plugins/<Name>/build/<Manufacturer> - VST - <Name>/` with `plugin.json`, `version.xml`, `VST/<slug>-arm32.so`, `VST/<slug>-arm64.so`, `Plugin Skins/`, and `Content/` (verbatim copy of the project's `Content/`, if it has one).
## Fixing failures
- **Compiler errors**: read them verbatim; they are from Clang. Usual causes: wrong framework method names (check `framework/mpc_plugin.h`), missing `#include`, narrowing conversions in `{}` initialisers, unused-variable warnings are not errors.
- **Linker `undefined symbol`**: a library or OS function that the MPC does not provide. Only the C and C++ standard libraries are available; compile third-party DSP sources into `src/`.
- **Validator errors**: the message says what to change (`uid` mismatch, folder name, `numOutputs`, glibc too new, missing export). `uid` in `plugin.json` must equal `MPC_FOURCC(...)` in the C++; `name`/`manufacturer` in `plugin.json` must equal `PluginInfo::name`/`vendor`.
- **Host-sim dump fails** (so no `params.json`): the plugin crashes at load. Run `.sdk-tools/host_sim build/native/<slug>.dylib test --verbose` to see which opcode.
- **Zig missing / no network**: install Zig from ziglang.org, put it on PATH or set `ZIG=`.
Build until there are no errors and the validator prints only OK lines (warnings acceptable if understood). Then run the `mpc-plugin-test` skill.
Details: `docs/building.md`.
## Desktop VST2 (listen on this computer, e.g. in Reaper)
`python tools/build.py plugins/<Name> --target desktop` builds a generic, UI-less VST2 for the current computer into `plugins/<Name>/build/desktop/` (macOS: signed universal `<Name>.vst`; Windows/Linux: a folder with the `.dll`/`.so`, `plugin.json` and `Content/`). Tell the user where to copy it (printed at the end), that the host shows its own parameter list, and that the host must support VST2. This is not a substitute for the MPC build and `host_sim` checks.
© inmusic-software · MIT · inmusic-software/mpc-plugin-builder-sdk