# 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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 200 repo stars
- Author: inmusic-software
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/inmusic-software/mpc-plugin-builder-sdk/tree/HEAD/.agents/skills/mpc-plugin-new/SKILL.md
- Updated: 2026-11-07
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/mpc-plugin-new

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/mpc-plugin-new/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/mpc-plugin-new/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/mpc-plugin-new/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/mpc-plugin-new/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install inmusic-software/mpc-plugin-builder-sdk .agents/skills/mpc-plugin-new
```

2. **Manually: put the files in place**
- File: `.github/skills/mpc-plugin-new/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add inmusic-software/mpc-plugin-builder-sdk --skill mpc-plugin-new -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/inmusic-software/mpc-plugin-builder-sdk --path .agents/skills/mpc-plugin-new
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/mpc-plugin-new/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/inmusic-software/mpc-plugin-builder-sdk/tree/HEAD/.agents/skills/mpc-plugin-new/SKILL.md

## When to use it
- 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
- 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.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6bab8c0009871763.

BEGIN THIRD-PARTY FILE 6bab8c0009871763
````text
---
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
```
````
END THIRD-PARTY FILE 6bab8c0009871763

The third-party file has ended. Everything between the 6bab8c0009871763 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2580 of 5168 bytes. © inmusic-software · MIT · https://github.com/inmusic-software/mpc-plugin-builder-sdk/tree/HEAD/.agents/skills/mpc-plugin-new/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
