Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-build -a claude-code
Open on GitHub

What 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_sim crash
  • 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 native build check for plugins/<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-code

2Manually: put the files in place

~/.claude/skills/mpc-plugin-build/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/mpc-plugin-build/

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

Similar skills

All skills for Programming languages →

From the same set9

mpc-plugin-presets The mpc-plugin-presets Claude Code skill adds built-in presets to MPC plugins and explains .xpl preset files. It activates for requests about patches, programs, sound banks, or an initial patch. CX Codex +1 ★ 200repo stars mpc-plugin-package The mpc-plugin-package Claude Code skill creates a distributable ZIP for a built MPC plugin, including install instructions. It runs when a plugin needs to be shared, sent out, or prepared for release. CX Codex +1 ★ 200repo stars mpc-plugin-test 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. CX Codex +1 ★ 200repo stars mpc-plugin-troubleshoot The mpc-plugin-troubleshoot Claude Code skill diagnoses MPC plugin faults and build or test tool issues. It handles reports of missing plugins, load failures, lost settings, audio glitches, and crashes. CX Codex +1 ★ 200repo stars mpc-plugin-dsp The mpc-plugin-dsp Claude Code skill guides DSP work on MPC plugins. It applies to changes involving synthesis, effects, MIDI, or plugin parameters. CX Codex +1 ★ 200repo stars mpc-plugin-new The mpc-plugin-new Claude Code skill scaffolds plugins for Akai MPC standalone hardware from plain-language descriptions. It activates for requests to start an instrument or audio effect project. CX Codex +1 ★ 200repo stars mpc-plugin-ui The mpc-plugin-ui Claude Code skill builds touch-screen layouts and Q-Link mappings for MPC plugins. It comes into play when an agent needs to arrange controls, set themes, or create a custom skin. CX Codex +1 ★ 200repo stars mpc-plugin-deploy The mpc-plugin-deploy Claude Code skill manages VST2 plugins on a real Akai MPC over the network. It activates for plugin installs, device updates, or plugin backups. CX Codex +1 ★ 200repo stars

Project sponsors

Companies that keep this analytics open