Your MPC, Your Rules (and Your Problem If It Crashes)
An open-source field guide to getting compatible third-party plugins onto a standalone MPC, building with AI coding agents, and respecting the people who made the tools in the first place.
Penemue Audio · November 2026 · Community guide, first edition
A lot of synthesizers have familiar ingredients: oscillators, envelopes, filters, modulation, distortion, delays. Spend enough time exploring vintage and modern software and you'll hear plenty of variations on the same sounds we've been buying in different packages since the 1990s and 2000s. That's funny, but it doesn't mean the products are interchangeable. There is an enormous difference between a basic sound recipe and a polished, dependable instrument.
The newly released inMusic MPC Plugin SDK lets developers and AI coding agents build instruments and effects for compatible standalone MPC hardware. This is a chance to make your own tools, contribute to preservation efforts, and investigate existing projects. It's not a license to take somebody else's code, firmware, artwork or commercial product.
This walkthrough is deliberately split into two tracks: install an already MPC-compatible third-party plugin first, then optionally build your own with an AI coding agent. You can finish the first track without developer mode or root access.
Before you touch anything: If you have a client session tomorrow, a tour set to perform, or a project due at midnight, finish your work first. Experimental plugins run inside the MPC application and can crash it. Back up your content and test only in a disposable project.
1. Know what “open source” buys you
An open-source license lets you study, use, modify or redistribute source code under stated conditions. It does not mean that related factory ROMs, firmware, preset libraries, samples, artwork, trademarks and commercial products are free to copy.
The official MPC Plugin SDK is MIT-licensed. Individual plugins may use MIT, GPL or other licenses, or may be closed source. Free to download and open-source are different things. Check the exact license of every dependency and of any assets in the package.
A faithful firmware emulator, a circuit-modelled recreation, a hardware-inspired synth, and an official manufacturer plugin are also different kinds of projects. Credit their respective makers accurately.
2. Verify your MPC and firmware
The official SDK supports compatible standalone MPC machines running MPC OS 3.10.1 or later with External Plugin Support enabled. It covers many earlier 32-bit ARM MPCs and newer 64-bit ARM models including the MPC XL. Verify the current compatibility list in the SDK readme before you build or install.
Check Preferences → Info for the firmware version. The official support FAQ describes third-party plugin support.
You need a supported MPC, your normal computer and a USB drive or other supported storage. No Linux modification is necessary for the standard external-plugin route.
3. Beginner route: install an existing compatible plugin
- Back up your projects, samples and presets to a separate location. Do not experiment on your only copy.
- On the MPC, open Preferences → Enhancements (Beta). Turn on Enable Enhancements and External Plugin Support and read the warning.
- Find a plugin package specifically compiled for the MPC. Browse official SDK examples or a community index such as Open MPC. Check the model/architecture, release date, license, required assets and reports of stability.
- On your USB drive, create a top-level folder named
VST2 Plugins— exactly that, including the space and capitalization. Copy the plugin's whole packaged folder under it, preserving the original directory structure. - Insert the drive, open the MPC instrument or insert browser, and look under External Plugins. Restart the MPC or remove/re-add the plugin if necessary.
- Test it in a new, empty project. Load it, play it, adjust controls, save, close, reopen and check that your work comes back. Then test it with a reasonable track count and monitor for glitches or crashes.
The usual SDK package looks like this:
USB DRIVE/
└── VST2 Plugins/
└── Maker - VST - Plugin Name/
├── plugin.json
├── VST/
│ ├── <slug>-arm32.so
│ └── <slug>-arm64.so
└── Plugin Skins/
├── TUI.json
└── Q-Links.json
The two binaries are named after the plugin's slug, one per architecture. Actual packages vary. Follow the plugin's own release instructions; don't rename binary files or invent missing manifests. The official install and test guide describes the supported layout.
Why you cannot
drag a desktop .vst3 onto the MPC
Standalone MPC hardware uses a Linux/ARM runtime and an MPC-specific plugin host. A Mac or Windows VST3 is not an MPC Linux ARM VST2 package. Renaming its file is not porting it. The sound engine may need recompiling and the UI needs adapting; closed-source software may not allow such changes or redistribution. In many cases, the sensible alternative is to use your desktop instrument alongside the MPC and record/bounce the audio.
4. Have Claude Code or Codex build the official example
Get the SDK onto the computer that runs your coding agent:
git clone https://github.com/inmusic-software/mpc-plugin-builder-sdk.git
cd mpc-plugin-builder-sdk
python3 tools/build.py examples/StereoDelayThe SDK requires Python 3.9+ and downloads build tooling on its first
run. Windows often uses python rather than
python3; let the documentation and your local environment
determine the right command. Build the StereoDelay
example before attempting a big synth port.
Open the SDK directory in Claude Code, Codex or another local coding agent that you intentionally authorize to use your computer. A web chat alone does not get access to your folders or MPC. Paste this:
AI setup prompt
I am developing for an Akai [MODEL] running [FIRMWARE], using a [MAC/WINDOWS/LINUX] computer. Read the official inMusic MPC Plugin SDK documentation and inspect the build environment. Verify the target architecture, Python and compiler requirements. Build and validate the SDK StereoDelay example, then run available simulator tests. Show me the finished package path and any errors. Do not modify MPC firmware, enable developer mode, access unrelated files, delete data, or overwrite existing plugin folders. Ask before writing to removable storage. Distinguish successful compilation from actual testing on my device.
Once the example works, copy its complete generated package into
VST2 Plugins, then try it in a scratch project.
5. Build a new instrument instead of borrowing somebody's IP
You can ask an agent for a custom synth without pretending it is a branded commercial product. Start small, then iterate from a stable build:
Original plugin prompt
Using only the official MPC Plugin SDK framework and compatible, properly licensed dependencies, create an original MPC synthesizer called First Light. Give it two oscillators (sine, triangle, saw, square), detune, resonant low-pass filter, ADSR envelope, tempo-synced LFO, MIDI note handling, master gain, touchscreen controls, Q-Link mapping, and eight original patches. Build for my MPC hardware, validate the package, and test note handling, parameter changes, preset save/restore, silence and stability in the host simulator. Explain CPU/memory tradeoffs. Do not copy proprietary code, artwork, patches, samples, or brand presentation. Keep all source and reproducible build steps. Report hardware verification as untested until I personally test it.
The SDK includes templates, testing tools and UI conventions. A coding agent can do a surprising amount of work, but it is not an independent source of truth about licensing, stability or fidelity.
6. Evaluate an existing open-source port honestly
Sometimes somebody has already done 90% of the difficult work. Sometimes the repository contains a promising DSP engine tied to a desktop UI framework that requires substantial adaptation. Sometimes an emulator depends on proprietary firmware the author deliberately does not distribute. Know the difference before investing a weekend.
Port feasibility prompt
Analyze [REPOSITORY URL] as a potential MPC plugin for [MODEL] on [FIRMWARE]. Read the exact license, contributor attributions, dependencies, supported processor architectures and build instructions. Classify the project as an emulator, model, original engine, port or inspired-by recreation; don't guess. Identify the work needed to adapt its audio engine and UI to the official inMusic SDK. Specify any ROM/firmware/samples required and whether the project has the rights to distribute them. Check for an existing MPC build or active port before recommending duplicate work. Estimate CPU/memory feasibility and create an evidence-linked plan. Do not copy protected assets or change my machine. If feasible, produce a reproducible, simulator-tested build and mark real-hardware status as unverified until tested.
The Penemue Audio discovery map is intended as a starting point for this research. A gap in the map means not yet found or verified, not that anyone owns an empty piece of intellectual property. Help us correct it.
7. What can break, and how to recover
Third-party MPC plugins run inside the host and are not isolated like separate applications. Possible problems include crashes, audio dropouts, stalled notes, CPU spikes, corrupted unsaved session state and projects that no longer load smoothly when a plugin goes missing.
Your first response to a failed plugin should be boring: remove the suspect plugin's folder from your test drive, restart, try a blank project, and confirm a known-good plugin still works. Back up first. Do not immediately root the device, edit system directories or replace the firmware because a browser entry is missing.
Developer mode and network deployment are advanced optional tools. The official SDK documents them, but they add access and security considerations absent from copying a package on removable storage. Do not leave an exposed development service enabled on a network you do not control.
Troubleshooting prompt
Plugin: [NAME / VERSION]. MPC: [MODEL / FIRMWARE]. Symptom: [EXACT BEHAVIOR]. Check the official SDK troubleshooting docs, CPU architecture, plugin manifest, package directory layout, missing libraries, required assets and UI metadata. Begin with read-only tests on my computer. Give a reversible recovery plan. Do not alter firmware, enable root access, delete project content or change network services without specific approval. Separate confirmed results from hypotheses.
Session tomorrow? Delay the experiment. Open-source development is satisfying, but the main job of your studio instrument is to work when you need it.
8. Credit the engineers, and pay for good tools
There is a reason to support Native Instruments, Spectrasonics, Moog, Akai and the independent software developers whose work we emulate, study and expand. They built complex, playable, supported instruments — often after years or decades of engineering. The history behind modern recording technology is nearly a century of inventiveness, and most of that work was done without an AI assistant on standby.
Yes, open-source development can sometimes get you to a similar sound or effect. No, that does not make the original tool's workflow, physical controls, research, quality assurance, support or artistry irrelevant.
A nail gun and a hammer can both drive a nail. I'd still like to see somebody chisel with a nail gun.
Make tools. Credit tools. Share what you have the rights to share. Pay for quality when quality is what you need.
References and opportunities to contribute
- Official MPC Plugin SDK, license and examples
- Official SDK installation and testing documentation
- inMusic MPC 3.10.1 external plugin FAQ
- Open MPC community catalog
- Gearmulator: The Usual Suspects
- Penemue Audio's hardware emulation map and contribution portal
Independent educational guide, not manufacturer-approved support. Brand and product names belong to their owners. This guide does not distribute proprietary firmware, ROMs or third-party factory content. Features and compatibility may change; use the linked primary documentation to check the latest requirements.