mpc-plugin-presets — Claude Code skill for MPC 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.
MIT ★ 200 updated 2026-11-07
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-presets -a claude-codeWhat mpc-plugin-presets does
The skill walks through adding built-in programs to an MPC plugin and checking them after a rebuild. First, find the parameter order with .sdk-tools/host_sim build/native/<slug>.dylib dump or by reading the constructor’s addParam calls. Add an addProgram call for each preset after those parameters, using plain values in their original units rather than normalized values. The first program is recommended as Init.
Each program needs a complete parameter list in the right order. After rebuilding, use dump to see program names, then run test. MPC .xpl files are user-saved presets tied to the plugin’s device path; the SDK does not create them, and they are not browsed from a plugin folder. Format details are in docs/presets.md.
What it helps with
- add built-in programs to an MPC plugin
- find the parameter order for each preset
- check program names after rebuilding
- understand how MPC
.xplfiles are handled
Example prompts for the agent
- Add built-in presets to my MPC plugin, including an
Initprogram. - Show how to set program values in the correct parameter order.
- Explain how MPC
.xplpreset files work.
How to install mpc-plugin-presets
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-presets -a claude-code2Manually: put the files in place
~/.claude/skills/mpc-plugin-presets/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mpc-plugin-presets/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-presets -a codex2Manually: put the files in place
.agents/skills/mpc-plugin-presets/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-presets -a cursor2Manually: put the files in place
.cursor/skills/mpc-plugin-presets/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inmusic-software/mpc-plugin-builder-sdk .agents/skills/mpc-plugin-presets2Manually: put the files in place
.github/skills/mpc-plugin-presets/SKILL.md1Skills CLI (Vercel)
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-presets -a gemini-cli2Platform CLI
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .agents/skills/mpc-plugin-presetsManually: put the files in place
.devin/skills/mpc-plugin-presets/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-presets
How do I install mpc-plugin-presets in Claude Code?
Run npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-presets -a claude-code. The skill file will be at ~/.claude/skills/mpc-plugin-presets/SKILL.md.
What does mpc-plugin-presets do?
It guides adding built-in programs to MPC plugins, ordering their parameter values, and checking the result after a rebuild. It also explains the role and limits of user-saved .xpl files.
How do I verify MPC built-in presets?
After rebuilding, run dump to list program names, then run test.
Source text
SKILL.md · MIT
---
name: mpc-plugin-presets
description: Add factory presets (built-in programs) to an MPC plugin, or explain MPC preset (.xpl) files. Use when the user asks for presets, patches, programs, an init patch or a sound bank for their plugin.
---
# Presets
The reliable mechanism is built-in programs declared in code. They appear in the MPC's preset selector and are stored by number in projects.
1. Get the parameter order: `.sdk-tools/host_sim build/native/<slug>.dylib dump` (or read the constructor's `addParam` order).
2. In the constructor, after all `addParam` calls, add one `addProgram("Name", { plain values in parameter order })` per preset. Values are plain (Hz, dB, 0/1 for bools, choice index for choices), not normalised. Make program 0 a sensible "Init".
3. Keep lists complete and in order; a comment per value helps future edits. 8–16 presets covering distinct uses is a good factory set.
4. Rebuild, then verify with `dump` (it lists program names) and `test`.
`.xpl` preset files are the MPC's user-saved preset format; they are tied to the plugin's path on the device and are not browsed from inside a plugin folder, so the SDK does not generate them. Details and the XML layout: `docs/presets.md`.
© inmusic-software · MIT · inmusic-software/mpc-plugin-builder-sdk