apc-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Model Context Protocol (MCP) server for commercial audio plugin development — from scaffold to validated, packaged release.
apc-mcp
apc-mcp is a Model Context Protocol server for commercial audio plugin development. It equips any MCP-compatible AI coding agent with 10 canonical MCP tools and 4 native / slash commands (prompts/list & prompts/get) to scaffold, design, synchronize parameters, configure, build, test, lint, validate, package, and locally install CMake audio plugins for JUCE + JIVE, standard JUCE, JUCE WebView, JUCE ARA effects, CLAP, VST3, LV2, and standalone applications.
It wraps your toolchain — it does not ship one. apc-mcp invokes
cmake, your C/C++ compiler,ctest,clang-format,pluginval, andclap-validatordirectly via argument arrays (never a shell), and resolves JUCE and JIVE deterministically via_tools/or~/.apc-mcp/deps/. What you need →
What's New in v2.0.0
End-to-end commercial shipping pipeline (
apc→apc-add-param→apc-ship): Scaffold a JUCE 9 + JIVE v2.0.1 plugin, atomically sync APVTS parameters with XML/JSON UI, and runRelease Build → clang-format → pluginval (strictness 5) → dist/ Package → Local VST3 Installin one tool call.Built-in
apc::dspheader-only DSP kit: Vendored fromNoizefield/audio-plugin-coder(MIT) intotemplates/common/dsp/(ParamSmoother,DenormalGuard,LockFreeFifo,Biquad,Svf,SoftClipper,DryWet,Oversampler2x) and linked by default (APC_USE_DSP_KIT=ON) in all JUCE scaffolds.Optional
apc::licenselicensing seam: Vendored intotemplates/common/licensing/(ApcLicense.h,ApcCanonicalJson.h),OFFby default (APC_USE_LICENSE_SEAM=OFF), never gates the audio path, and accepts an injectedISignatureVerifier.Expanded formats & scaffolds: Dedicated JUCE ARA effect (
type="ara"), native CLAP (type="clap"), pure C11 LV2 (type="lv2"), standalone GUI app (type="standalone"), and embedded HTML/CSS/JS WebView (ui="webview").Security & supply-chain hardening: Symlink-aware project containment (
assertWithinProject()),O_NOFOLLOW/O_EXCLfile writes,-Dcode-loading variable blocklist, honestisErrorreporting, and an SPDX license gate (npm run licenses).
Related MCP server: MCP-CMake
Quickstart (60 Seconds to DAW)
1. Add apc-mcp to your MCP client
{
"mcpServers": {
"apc-mcp": {
"command": "npx",
"args": ["-y", "github:sgm-audio/apc-mcp"]
}
}
}Check the running version with npx -y github:sgm-audio/apc-mcp --version. Client config variants →
2. Initialize a project directory
mkdir my-plugins && cd my-plugins
echo '{}' > apc-mcp.json3. Run the /apc:new → /apc:ui → /apc:ship slash-command workflow
MCP clients automatically expose apc-mcp's registered MCP Prompts as native / slash commands:
Slash Command | Arguments | What It Executes |
| (none) | Runs |
|
| Runs |
|
| Reads |
|
| Runs |
/apc:new name="TapeEcho" style="fx"
/apc:ui design="Add a warm saturation drive knob (0 to 24 dB), feedback slider (0 to 95 %), and bypass toggle"
/apc:ship version="1.0.0"Which AI Coding Tools Work with apc-mcp?
apc-mcp is client-agnostic and communicates over standard MCP stdio:
Client / Host | Transport | How |
Claude Desktop / Claude Code |
| Native MCP tools + |
Cursor |
| Native MCP tools + |
VS Code (Copilot / Agent) |
| Native MCP tools + prompts via |
Windsurf / Continue |
| Native MCP tools via |
OpenCode |
| Native MCP tools via |
Antigravity / Gemini / Codex |
| Standard MCP tool calls + bundled |
Creating and Shipping a JUCE + JIVE Plugin
apc defaults to type="juce" and ui="jive" when omitted, generating a deterministic CMake 3.22+ project powered by JUCE 9.0.3 and JIVE v2.0.1 (declarative XML layouts + JSON stylesheets).
1. Architecture & Hot-Reload (Debug vs. Release)
Debug Hot-Reload (
#if JUCE_DEBUG):PluginEditorconfiguresjive::SourceRootpointing toSource/UIon disk (APC_JIVE_UI_DIR). EditingSource/UI/MainView.xmlorSource/UI/Styles.jsonupdates the open plugin window live in your DAW or standalone host without recompiling C++.Release Embedded Assets (
CMAKE_BUILD_TYPE=Release):Source/UI/MainView.xmlandSource/UI/Styles.jsonare compiled directly into the binary viajuce_add_binary_data(<PluginName>_JiveData NAMESPACE <PluginId>_JiveData). The shipped.vst3/.component/.lv2bundle has zero external file dependencies and can be moved to any machine.Compile-Time Toggle (
-DAPC_USE_JIVE=ON|OFF): Generated JIVE projects exposeoption(APC_USE_JIVE "Enable JIVE declarative XML/JSON UI" ON). Passing-DAPC_USE_JIVE=OFFskips fetching/linkingjive::jive_layoutsandjive::jive_style_sheetswithout polluting global include paths and falls back tojuce::GenericAudioProcessorEditor.Warnings-as-Errors & Portability: All generated plugin sources compile with
-Wall -Wextra -Werror(GCC/Clang) or/W4 /WX(MSVC). Release Windows builds statically link the MSVC runtime (/MTviaMultiThreaded$<$<CONFIG:Debug>:Debug>), and macOS builds support universal binaries (CMAKE_OSX_ARCHITECTURES="arm64;x86_64"or-DAPC_MACOS_UNIVERSAL=ON).
2. Deterministic Dependency Caching (_tools/ vs. ~/.apc-mcp/deps/)
Generated CMakeLists.txt files never fetch unpinned main/master branches. Dependencies resolve in strict priority order:
Explicit CMake / environment override:
-DJUCE_DIR=/path/to/JUCE/$ENV{JUCE_DIR}and-DJIVE_DIR=/path/to/JIVE/$ENV{JIVE_DIR}.Project-local
_tools/override:${CMAKE_SOURCE_DIR}/_tools/JUCE,_tools/JIVE,_tools/clap, and_tools/lv2.Global user cache (
~/.apc-mcp/deps/):~/.apc-mcp/deps/JUCE,~/.apc-mcp/deps/JIVE,~/.apc-mcp/deps/clap, and~/.apc-mcp/deps/lv2(APC_DEPS_CACHE_DIR).Pinned CMake
FetchContentfallback (populated into~/.apc-mcp/deps/on first run):JUCE
9.0.3: commit SHAbe29c81492b6151c8ea8d14c840e1311963b3a83JIVE
v2.0.1: commit SHA693788a539eb42b9c15848706f9ceae43ee60084Supports offline air-gapped builds via
-DFETCHCONTENT_FULLY_DISCONNECTED=ONonce~/.apc-mcp/deps/or_tools/is populated.
Built-in DSP Kit (apc::dsp) & Optional Licensing Seam (apc::license)
Every newly scaffolded JUCE project copies common/dsp/ and common/licensing/ into the project root:
APC_USE_DSP_KIT(defaultON): LinksAPC::dsp(header-only, std-only C++17, zero JUCE dependency) and definesAPC_HAS_DSP_KIT=1. IncludesParamSmoother.h,DenormalGuard.h,LockFreeFifo.h,Biquad.h,Svf.h,SoftClipper.h,DryWet.h,Oversampler2x.h, and the umbrellaapc_dsp.h. Pass-DAPC_USE_DSP_KIT=OFFto disable. See the DSP kit README.APC_USE_LICENSE_SEAM(defaultOFF): When enabled (-DAPC_USE_LICENSE_SEAM=ON), addscommon/licensing/to the target's private include path and definesAPC_HAS_LICENSE_SEAM=1. ProvidesApcLicense.handApcCanonicalJson.hwith an injectedapc::ISignatureVerifier(no crypto library bundled; never gates the audio path). See the licensing seam README.
Supported Plugin Formats & Platforms
Scaffold | Formats | Windows | macOS | Linux | Notes |
| VST3, LV2, Standalone (+ AU on macOS via | ✅ | ✅ | ✅ | Supports |
| VST3 | ✅ | ✅ | ✅ | Focused JUCE VST3 target |
| VST3, AU ( | ✅ | ✅ | ✅ (VST3) | Requires external |
| CLAP ( | ✅ | ✅ | ✅ | Native C/C++ against |
| LV2 ( | ✅ | ✅ | ✅ | Zero-dependency pure C11 with Turtle metadata |
| Standalone GUI app | ✅ | ✅ | ✅ |
|
Manual Tool Reference
See the full Tool reference for the 10 canonical tools (apc, apc-add-param, apc-ship, apc-doctor, apc-cfg, apc-build, apc-test, apc-lint, apc-val, apc-list). The former audio_plugin_* names remain available as deprecated compatibility aliases.
apc
Scaffolds a new plugin or application into <pluginsDir>/<name>, registers add_subdirectory(...) in the root CMakeLists.txt, copies common/dsp/ and common/licensing/ for JUCE projects, and initializes ~/.apc-mcp/deps/.
Parameter | Type / Default | Description |
|
| Project root containing |
|
| Plugin name ( |
|
| Target scaffold. Defaults to |
|
| UI framework for |
|
| Seeds initial DSP & JIVE controls: |
|
| Vendor/company name embedded in plugin metadata (up to 128 chars, non-ASCII supported). |
|
| Short plugin description (up to 512 chars, non-ASCII supported). |
|
| Semicolon-separated JUCE format override for |
For type="ara", obtain the external ARA SDK with its submodules initialized, then configure it before building. JUCE 9.0.3 requires ARA SDK 2.2.0+ (verified with releases/2.3.0):
git clone --depth 1 --recurse-submodules --branch releases/2.3.0 \
https://github.com/Celemony/ARA_SDK.git /absolute/path/to/ARA_SDKapc-cfg(projectPath="/path/to/my-plugins", options="-DAPC_ARA_SDK_PATH=/absolute/path/to/ARA_SDK")The path must be the SDK root containing ARA_Library/PlugIn/ARAPlug.h and ARA_API/ARAInterface.h. Generated CMake fails early with FATAL_ERROR for an unset, empty, or incomplete SDK, then calls juce_set_ara_sdk_path(...) before juce_add_plugin(...). ARA uses FORMATS VST3 AU with IS_ARA_EFFECT TRUE; do not pass formats="ARA".
Return payload: Markdown summary containing the created plugin directory, template and style preset used, root CMakeLists.txt registration status, ~/.apc-mcp/deps/ cache initialization status, and the scaffolded file tree.
apc-add-param
Atomically synchronizes a new automatable parameter across C++ APVTS, JIVE XML layout, and JSON stylesheet.
Parameter | Type / Default | Description |
|
| Project root (auto-detected from CWD). |
|
| Target plugin name under |
|
| Unique APVTS parameter ID and JIVE component ID ( |
|
| Display name (e.g. |
|
| Minimum value (must be |
|
| Maximum value. |
|
| Initial default value ( |
|
| Optional unit label (e.g. |
|
| JIVE element to inject: |
Return payload: Confirmation listing the updated Source/PluginProcessor.cpp (createParameterLayout), Source/UI/MainView.xml binding, Source/UI/Styles.json (#<id>) rule, and XML well-formedness / JSON validity verification.
apc-ship
Executes the end-to-end commercial shipping pipeline in a single call: Stage 1 (Release Configure & Build) → Stage 2 (clang-format Source Lint) → Stage 3 (pluginval --strictness-level 5 --validate-in-process) → Stage 4 (dist/<Name>-<Version>-<OS>/ Packaging + INSTALL.txt + macOS ad-hoc codesign --force --deep -s -) → Stage 5 (Local OS VST3 Install).
Parameter | Type / Default | Description |
|
| Project root (auto-detected from CWD). |
|
| Semantic version string for |
|
| Copies the validated |
Return payload: Stage-by-stage pass summary with exact dist/ package paths and local VST3 install paths, or structured compiler/linter/validator diagnostic lines (isError: true) when any gate fails so the calling agent can self-heal immediately.
apc-doctor
Inspects the local build environment and initializes the global dependency cache.
Parameter | Type / Default | Description |
|
| Optional project root to check for project-local |
Return payload: Status report for cmake, the C++20 compiler (c++ / clang++ / g++ / cl), ~/.apc-mcp/deps/ initialization, JUCE SDK path, JIVE framework path, pluginval availability, OS VST3 directory, and actionable installation commands for any missing tool.
Repository Architecture
apc-mcp/
├── index.js # MCP server (10 tools, 4 prompts, containment & validation)
├── pluginval.js # Cross-platform pluginval invocation & strictness checks
├── templates/
│ ├── juce/ # Standard JUCE 9 plugin template
│ ├── juce-jive/ # JUCE 9 + JIVE v2.0.1 declarative UI template
│ ├── juce-webview/ # JUCE 9 + embedded HTML/CSS/JS WebView template
│ ├── ara/ # JUCE 9 ARA effect template
│ ├── clap/ # Native CLAP plugin template
│ ├── lv2/ # Pure C11 LV2 plugin template
│ ├── standalone/ # JUCE 9 standalone GUI application template
│ └── common/ # Vendored apc::dsp kit + optional apc::license seam
├── skills/ # Bundled audio-plugin engineering skills
├── docs/ # Architecture, toolchain, security, and release docs
├── scripts/ # Smoke builds, docs/license gates, release script
└── tests/ # Node test suite (npm test)Distribution, OS Install Paths & Limitations
Packaging Output (dist/)
Running apc-ship or cmake --build build --config Release --target package produces a self-contained distribution folder:
dist/<PluginName>-<Version>-<macOS|Windows|Linux>/
<PluginName>.vst3
<PluginName>.component # macOS when AU is enabled in FORMATS
INSTALL.txtStandard End-User Plugin Paths
OS | Format | Destination |
macOS | VST3 |
|
macOS | AU |
|
Windows | VST3 |
|
Linux | VST3 |
|
Linux | LV2 |
|
Known Limitations
macOS Ad-Hoc Signing vs. Public Notarization:
apc-shipand the CMakepackagetarget runcodesign --force --deep --sign -on macOS bundles so they load locally without Gatekeeper quarantine failures. That ad-hoc signature is local-only and never valid for distribution — it confers no Gatekeeper trust anywhere else. Public distribution on macOS requires an Apple Developer ID Application certificate, hardened-runtime signing,xcrun notarytool submit --waitandxcrun stapler staple; Windows public distribution requires a trusted code-signing certificate (EV preferred) with timestamped Authenticode (signtool sign /tr ... /td sha256 /fd sha256). The full sequences, a fail-closed signing script for each platform, and an example release workflow are in Release signing & distribution.ARA SDK requirement:
type="ara"generates a JUCE ARA effect scaffold, but the ARA SDK is external and is not bundled. Configure with-DAPC_ARA_SDK_PATH=/absolute/path/to/ARA_SDKbefore building; the path must point to a complete SDK root with initializedARA_LibraryandARA_APIheaders. ARA is an effect mode (IS_ARA_EFFECT TRUE) layered on VST3/AU, never aFORMATSvalue.Headless Linux Display & WebView:
pluginvalinstantiates the plugin GUI editor and requires an X11 display on Linux (wrap headless CI runs inxvfb-run -a).ui="webview"requireslibwebkit2gtk-4.1-dev/libgtk-3-devon Linux. Generated JUCECMakeLists.txtfiles automatically defineJUCE_ALSA=0whenlibasound2-devis absent on headless Linux containers.
Documentation
Guide | What it covers |
Client setup, first plugin, artefacts | |
All 10 canonical tools, deprecated aliases, native slash commands, arguments, scaffold types | |
| |
Prerequisites, SDK discovery, platform notes, quirks | |
FAQ and common errors | |
Threat model, defence layers, the 1.4.0 / 1.5.0 upgrade notice | |
Tests, contributing, release process | |
Verification baseline, what is done, what is left | |
Release history and the full documentation map |
Version 2.0.0 is current; avoid 1.4.0 / 1.5.0 on untrusted input. See SECURITY.md and CONTRIBUTING.md.
Acknowledgments
JUCE Team — the cross-platform audio plugin framework (JUCE)
ImJimmi — declarative XML/JSON UI via JIVE
Noizefield —
audio-plugin-coder(MIT), source of the vendoredapc::dspkit andapc::licenseseam
License
MIT © 2026 Scott Mills. See LICENSE. Note: apc-mcp itself is MIT, while plugins built with JUCE inherit JUCE's dual license (AGPLv3 free, or a JUCE commercial license for closed-source distribution).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that exposes REAPER digital audio workstation functionality through a clean API interface, enabling programmatic control of 169+ REAPER operations across track management, MIDI editing, effects, automation and more.91MIT
- FlicenseNot gradedqualityDmaintenanceA Gradio-based MCP server for comprehensive CMake project management that enables configuring, building, and testing CMake projects with preset support, error analysis, and LLM-friendly output formatting. Provides both web UI and MCP protocol access for streamlined C++ development workflows.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.-
- AlicenseAqualityDmaintenanceMCP server that bridges Ableton Live with AI models, enabling real-time project inspection and control such as track overview, device parameters, and audio analysis.1273 PyPI1MIT