mpc-plugin-new — Claude Code skill for MPC plugins
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.
MIT ★ 200 updated 2026-11-07
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a claude-codeWhat mpc-plugin-new does
The skill turns a description of a synth, drum machine, sequencer-instrument, or audio effect into an Akai MPC plugin project. Before creating files, the agent settles the plugin and manufacturer names; the manufacturer appears on the device and forms part of the plugin’s permanent identity.
The tools/new_plugin.py script creates a scaffold with plugin.json, a C++ source file, ui.json, and README.md. The agent writes code using the SDK and DSP helpers, sets up the controls, then builds and tests the project with tools/build.py and .sdk-tools/host_sim. Build and test cycles continue until errors and failed checks are fixed.
Python and the SDK tools in the repository are required to create the project. Running the finished plugin on MPC requires MPC OS 3.10.1 or later and External plugin support enabled; copy the output folder to VST2 Plugins on a drive. Renaming after the build changes the permanent uid and parameter identifiers, so the names are settled beforehand.
What it helps with
- scaffold an Akai MPC synth or drum machine
- organize plugin controls into UI pages
- build and test a new MPC plugin
- prepare a plugin folder for transfer to a drive
Example prompts for the agent
- Create an Akai MPC synth called Wobble Bass by Acme Audio.
- Start a drum machine project named Dust Kit, with North Sound as the manufacturer.
- Build a Tape Echo effect for my Amber Audio brand and test it.
How to install mpc-plugin-new
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a claude-code2Manually: put the files in place
~/.claude/skills/mpc-plugin-new/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mpc-plugin-new/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a codex2Manually: put the files in place
.agents/skills/mpc-plugin-new/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a cursor2Manually: put the files in place
.cursor/skills/mpc-plugin-new/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inmusic-software/mpc-plugin-builder-sdk .agents/skills/mpc-plugin-new2Manually: put the files in place
.github/skills/mpc-plugin-new/SKILL.md1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a gemini-cli2Platform CLI
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .agents/skills/mpc-plugin-newManually: put the files in place
.devin/skills/mpc-plugin-new/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-new
How do I install mpc-plugin-new in Claude Code?
Run npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a claude-code. The skill file will be at ~/.claude/skills/mpc-plugin-new/SKILL.md.
What does mpc-plugin-new do?
It scaffolds an Akai MPC plugin project from an instrument or effect description, then guides the agent through writing code, configuring the UI, building, and testing it.
What does mpc-plugin-new need to work?
Project creation requires Python and the SDK tools in the repository. Running the plugin on an MPC requires MPC OS 3.10.1 or later, with External plugin support enabled.
Source text
SKILL.md · MIT
--- name: mpc-plugin-new description: Create a new MPC plugin project from a plain-language description (a synth, drum machine, sequencer-instrument or audio effect for Akai MPC standalone hardware). Use when the user asks to make, start, scaffold or build a new plugin, or describes an instrument or effect they want on their MPC. --- # Create a new MPC plugin You turn a description into a complete plugin project under `plugins/<Name>/` that builds, tests and packages with the SDK tools. Work in this order; do not skip the build and test steps. ## 1. Decide the shape (ask only if truly ambiguous) From the description, settle: - **Kind**: `instrument` (makes sound from MIDI notes: synths, drum machines, samplers, sequencer-instruments) or `effect` (processes the track's audio; receives NO MIDI). An arpeggiator or step sequencer must be an instrument that makes its own sound, because plugins cannot send MIDI to the MPC. - **Name** (short, 1–3 words) and **manufacturer** (the user's name or brand). See "Confirm the manufacturer and plugin name" below; never invent a generic manufacturer such as "MPC Vibecoder". - **Parameters**: 6–24 is typical. Each gets a short screen name (≤ 12 chars), a kind (float / int / bool / choice), range, unit, default. Group them into pages of ≤ 16 for the UI. - **Channels**: instruments 0 in / 2 out (multi-out: 4, 6 or 8 outs as stereo pairs); effects 2 in / 2 out. ### Confirm the manufacturer and plugin name The manufacturer name appears on the MPC, in the folder name and in the plugin's permanent identity, so it must be a real, deliberate choice. - If the user's prompt already gives their name or brand (e.g. "by Acme Audio"), use it and do not ask again. - If it does not, **stop and ask before scaffolding**: "What name should appear as the manufacturer of this plugin? This is usually your name or your brand." - In the same message, show the plugin name you propose (e.g. "I'd call the plugin **Wobble Bass**") and invite the user to change it. If they gave a name, show that instead and still allow changes. - Wait for the answer. Only continue once both names are settled. If the user declines to give a manufacturer, ask once more explaining that it is shown on the device and is hard to change later; only then accept their stated preference. - Do not rename after the build: `uid`, folder and `plugin.json` are derived from these names (see the "Identity is permanent" rule in AGENTS.md). ## 2. Scaffold ``` python tools/new_plugin.py "<Name>" --vendor "<Manufacturer>" --kind instrument|effect ``` This creates `plugins/<Name>/` with `plugin.json`, `src/<Class>.cpp`, `ui.json`, `README.md`. The printed `uid` is already written into both `plugin.json` and the C++ `MPC_FOURCC(...)`; they must stay equal. ## 3. Write the plugin Edit `src/<Class>.cpp`. Read `framework/mpc_plugin.h` once (it is short) and follow `docs/dsp-cookbook.md`. Use the helpers in `framework/dsp/` (`oscillator.h`, `svf.h`, `adsr.h`, `delay_line.h`, `smoother.h`, `voice.h`, `lfo.h`, `biquad.h`, `tempo.h`, `math.h`) rather than writing filters and envelopes from scratch. Study `examples/SimpleSynth`, `examples/StereoDelay` and `examples/DrumSynth` for structure. Rules that are not negotiable: - No allocation, locks, logging or file I/O inside `process()`. Allocate in `prepare()`. - Treat `maxBlockSize` as a maximum; `ctx.numFrames` varies between 32 and 512. - Parameter 0 gets nudged by the host on every load: make it harmless (master volume) and keep `parameterChanged()` side-effect free. - Clamp everything that feeds a filter or a divide. Reset state in `reset()`. - Keep CPU modest: the MPC is far slower than a laptop. Per-block coefficient updates, per-sample arithmetic only. - Parameter `id` strings and the `uid` are permanent once users have projects. Then edit `ui.json` using the `mpc-plugin-ui` skill: give every control a kit widget (`knob`, `fader` or `switch`, see its heuristics) instead of the generic slider, and pick one theme. Then write `README.md` (what it does, the parameter list, tips). If the plugin needs sample, wavetable or other data files, put them in `plugins/<Name>/Content/` and load them with `mpc::contentPath(...)` / `dsp::loadWav` (see the `mpc-plugin-dsp` skill); never use absolute paths. ## 4. Build, test, iterate ``` python tools/build.py plugins/<Name> .sdk-tools/host_sim "plugins/<Name>/build/native/<slug>.dylib" test --seconds 3 --wav plugins/<Name>/build/test.wav ``` (`.so` on Linux, `.dll` on Windows.) Fix every compiler error and every `FAIL` in the report; take `WARN` lines seriously (silence, clipping, CPU). Rebuild until clean. See the `mpc-plugin-build` and `mpc-plugin-test` skills. ## 5. Hand over Tell the user: the output folder path (`plugins/<Name>/build/<Manufacturer> - VST - <Name>/`), how to copy it to `VST2 Plugins` on a drive, that the MPC needs MPC OS 3.10.1 or later, and that External plugins must be enabled on the device (Preferences → Enhancements (Beta) → Enable Enhancements and External Plugin Support), and offer to package it (`mpc-plugin-package` skill). Summarise the parameters and pages you created.
© inmusic-software · MIT · inmusic-software/mpc-plugin-builder-sdk