About
What NuePlugin is.
NuePlugin turns a plugin you own into a plugin you made. Your own coding agent does the work on your Mac, through our MCP. You get a VST/AU that is yours, and a community of matches to browse.
How it works with plugins you own
01
It works on plugins installed on your Mac, and you pick which one.
02
Measuring, fitting and rendering happen on your Mac. Audio never leaves it.
03
Matches are named for what they do, not for what they were matched against.
04
Community matches pass automatic review and are signed once, by us, so a listing is the same everywhere.
What it can and can't match
- Exact
- Linear blocks: EQ, delay, unmodulated reverb.
- Impulse response and null-test depth.
- Identical.Shipping.
- Fitted
- Fixed-setting compression, saturation, preamps.
- Gain-trajectory error in dB on programme material.
- Within a stated dB.Shipping.
- Campaign
- Full-control-surface dynamics: classic feedback and opto-style compressors.
- A long fitting campaign across the whole control surface.
- May not converge. It tells you before it starts.Case by case.
- Perceptual
- Doublers, modulated reverb, pitch.
- Stereo correlation, per-band width, modulation rate and depth.
- Sounds the same.In progress. Reported as D, never hidden.
- —Not offered
- Neural-network plugins, spectral repair, pure randomness.
- Nothing to measure against.
- None. The gate says no up front.Not attempted.
Questions
Do I need to know DSP?
No. Your agent does the work. You listen, and you read the report.
Does my audio leave my Mac?
Never. Measuring, fitting and rendering all happen locally. Only the format file and its report go to the community, and only if you choose to publish.
How do I start?
Install the MCP with one command, open the coding agent you already use, and name a plugin you own.
What does it cost?
Free. Bring your own agent. The local tools and the community cost nothing.
Which agents?
Any coding agent that speaks MCP: Claude, ChatGPT and Codex, Kimi, and the rest. If it can call MCP tools, it works.
Which formats?
VST3 and AU today, on macOS. CLAP is next. Community matches are also published as a small open format file the Player can load.
Is this legal?
You can only match plugins you own, on your own machine. The community never shows what a plugin was matched against, and names describe what a plugin does. We take down anything that crosses the line.
Community rules
- 01
No vendor names, product names or hardware model names, anywhere in a listing or its file.
- 02
No screenshots of other plugins, no photos of gear.
- 03
Every listing carries its report and its tier. Hiding a D is grounds for removal.
- 04
One signature for all community plugins. Listings are the same binary everywhere.
- 05
Be specific and be kind. Talk about sound, not about who made the reference.
Takedowns
We have a designated agent for takedown notices. A listing named in a notice comes down while we look, and stays down if it crossed the line. Counter-notices follow the usual process. How to send one is in the Terms.