Make your first MPC plugin with AI

For a first plugin, try a warm saturation effect for drums with Drive, Tone, Mix, and Output controls. A small project makes it easier to judge the sound and describe changes. You can build a synth instead; the next guide has more starting prompts.

You do not need to write C++. Your job is to describe the result, listen, and give feedback. The agent writes files, runs builds, and investigates errors. A successful build is a checkpoint: you still need to try the result on your MPC.

Use a compatible standalone MPC or Force with MPC OS 3.10.1 or later and External Plugin Support enabled. Check the linked Akai release notes for your model. This guide does not cover MPC Sample or computer-only MPC controllers.

• A Windows, macOS, or Linux computer with internet access and room for the SDK and tools.
• Claude Code or ChatGPT with Codex in a local project with file and command access. A text-only chat cannot perform the build for you.
• Access to your chosen coding agent. Check its current account requirements and usage limits; the SDK is free, but AI usage may cost money.
• A USB drive or SD card for the finished plugin. Network installation is optional.

Create a folder named MPC Projects on your computer. For Claude Code, open a local session in that folder. In the ChatGPT desktop app, choose Codex and open the folder. The official setup guides under Sources explain installation and signing in.

Paste the setup prompt below. It asks the agent to get the real SDK and check your tools. Python 3.9 or newer is required; the default SDK build can download its compiler on first use without Docker.

Read installation approvals before accepting them. If setup fails, keep the full error in the conversation and ask the agent to fix it. Let the agent handle technical commands.

Help me create a plugin for my standalone Akai MPC. I am a producer, not a programmer.

Use the official SDK: https://github.com/inmusic-software/mpc-plugin-builder-sdk

Get the SDK into this workspace without overwriting existing files. Read its AGENTS.md and the skills for this coding agent. Check my operating system, Python, and default build toolchain. Explain any installation I need to approve. Build and test the unchanged StereoDelay example to check the setup.

Do not connect to or modify my MPC yet. Tell me what passed and what still needs attention.

When setup works, paste this brief. Replace the brackets with your creator name, MPC model, and firmware. Your creator name becomes the manufacturer on the device; choose one you intend to keep.

Answer follow-up questions in musical terms: soft or aggressive, dark or bright, subtle or obvious. Ask for the simplest useful version when unsure.

Create an MPC effect called Warm Drive by [creator name]. I will test it on [MPC model] running [firmware version].

I want warm saturation for drums that becomes crunchy when pushed. Include Drive, Tone, Mix, and Output, sensible defaults, and readable touchscreen controls with Q-Link mappings. Avoid sudden volume jumps and keep CPU use modest.

Use the official SDK and its skills. Build the ARM targets, run validation and host-simulator tests, and investigate failures and warnings. Render a short audio example if possible. Do not call it hardware-tested. When checks pass, give me the exact install-folder path and a short listening checklist.

Use the installation guide next. Start with a saved test project and low listening volume. Compare the effect with bypass, move each control, and save and reopen the project.

Tell the agent what you hear: “Drive gets loud too quickly,” “Tone is too dark,” or “Mix clicks.” Change one thing at a time and keep the last working build. Once you have something useful, the sharing guide walks you into Creator Studio.