音のプラグイン倉庫くんAudio Plugin Soko-kun - A warehouse of open-source audio plugins
English

CautionThis platform is an unofficial, free service not affiliated with the developers of plugin formats or DAWs. It does not guarantee the safety of any plugin, so use plugins carefully and at your own risk.This platform is unofficial and does not guarantee the safety of any plugin, so use plugins carefully. What is Audio Plugin Soko-kun?

Submit a plugin

Plugins you can submit

This platform lists open-source audio plugins whose author administers the GitHub repository and submits it.

Supported formats: VST® 3 CLAP, LV2, Audio Unit

Before submitting, check that the repository and its latest release meet the listing conditions: https://audio-soko-kun.allegromoltov.jp/policy

This platform determines the formats, OS, architectures, and category of a plugin from the bundles in its zip archives. You do not need to enter them.

Do not include the word VST in the name of your plugin or repository. The VST 3 SDK does not allow VST in product names, and the review reports such a name as a recommendation.

Check your repository before a release

Before you publish a release, ask your AI agent to run submit_plugin in check mode. It checks the listing conditions on the latest release and reviews the latest commit of the default branch. It does not register the plugin. You can use check mode up to 5 times in 24 hours.

The review follows the review criteria, which are public on GitHub: https://github.com/AllegroMoltoV/audio-plugin-soko-kun/blob/main/docs/design/review-criteria.md

Check mode does not inspect the archives or the macOS signatures, because those checks download the files in GitHub Actions after registration. The agent shows what these checks require.

How to submit

Connect your MCP client to https://audio-soko-kun.allegromoltov.jp/mcp. In Claude Code, run:

claude mcp add --transport http audio-plugin-soko-kun https://audio-soko-kun.allegromoltov.jp/mcp

Sign in with your GitHub account from the MCP client. In Claude Code, run /mcp and choose audio-plugin-soko-kun. In Codex, connect with codex mcp add audio-plugin-soko-kun --url https://audio-soko-kun.allegromoltov.jp/mcp, then sign in with codex mcp login audio-plugin-soko-kun. This platform itself never gets write access to your GitHub repositories.

Ask the AI agent to submit your repository, for example: "Register the audio plugin in https://github.com/<owner>/<repository>".

After submitting

This platform registers the plugin as waiting for checks. Until a release passes the checks, the plugin does not appear in search or on its own page.

Checks run every 15 minutes and usually finish within a few hours.

This platform lists only releases that pass the checks. When you publish a new release on GitHub, this platform picks it up and checks it automatically. You do not need to submit it again.

To see the results, ask your AI agent to check your plugin with list_my_plugins, for example: "Check whether my plugin's new release is listed". The agent shows the state of each release, the reasons a release or a file is not listed, the review findings, and how to fix them.

Some releases wait for an administrator to confirm them. To explain the changes in such a release, open an issue in the repository of this platform: https://github.com/AllegroMoltoV/audio-plugin-soko-kun/issues

When a submission is refused

The AI agent shows the reason code and how to fix it. Fix the cause and submit again.

  • not_admin: You do not have admin permission on the repository. Ask an administrator of the repository to submit it.
  • private_repository, archived_repository: Make the repository public, or unarchive it.
  • no_license: Put a LICENSE file with an open source license at the root of the repository, then publish a new release.
  • license_unrecognized: GitHub cannot identify the license. Keep only the standard license text in LICENSE, move other notices to NOTICE or README, then publish a new release.
  • license_not_open: License the plugin under a license approved by the OSI or recognized as free by the FSF, then publish a new release.
  • no_release, no_verifiable_asset: Publish a release with the plugin files attached (up to 30 files).
  • no_archive: Attach the plugin bundles to the release as zip archives.
  • not_immutable: Turn on immutable releases in the repository settings, then publish a new release.
  • no_attestation: Add actions/attest-build-provenance to the release workflow so that every file, including installers, has an attestation, then publish a new release.
  • duplicate: The repository is already registered. Open its page from the search.
  • name_reserved: A listed plugin used this repository name before it was renamed. Rename the repository to a name that no listed plugin has used.
  • rate_limited: You can submit up to 10 times in 24 hours. Try again later.
  • invalid_url: Give the repository URL in the form https://github.com/<owner>/<repository>.
  • not_found: The repository was not found. Check the URL and that the repository is public.
  • unsupported_tag: Use a release tag with only letters, digits, ".", "-", and "_", up to 100 characters.
  • github_unavailable: GitHub did not respond normally. Try again later.

When a release or a file is not listed

list_my_plugins shows why a release or a file is not listed. The main reasons that the author fixes are the following.

  • vst2_detected: An archive contains a VST 2 bundle or entry point. Remove VST 2 from every archive, then publish a new release.
  • no_plugin_detected, no_plugin_in_archive: No supported plugin bundle was found in the archives. Put the built bundles in the zip archives. Source code archives need no change.
  • content_undetermined: An archive contains files that cannot be inspected, such as installers or nested archives. Put the plugin bundles directly in the zip archive.
  • macos_not_signed, macos_adhoc, macos_not_developer_id, macos_not_notarized: Sign the macOS bundles with a Developer ID certificate and notarize them with Apple.
  • declaration_mismatch, not_declared: The declarations in .audio-soko-kun/config.json and the inspected archives disagree. Fix the declarations, then publish a new release.
  • installer_not_guided: Installers are not guided. Users get the plugins from the zip archives.

Logo and description image

Authors can show one logo and one description image. Place the images in the .audio-soko-kun folder of the repository.

.audio-soko-kun/logo.png
.audio-soko-kun/image.gif
  • Logo: name the file logo. Keep it within 256 KB and 1,024 px on each side.
  • Description image: name the file image. Keep it within 1.5 MB and 4,096 px on each side. GIF images play as animations.

This platform does not accept SVG, which can contain scripts, so use the extension png, jpg, jpeg, gif, or webp.

This platform takes the images at the tag of the latest release, so publish a new release after you change an image.

This platform does not show images that do not meet these conditions, so check the conditions if an image does not appear.

.audio-soko-kun/config.json

Authors can declare the display name, the category, and the OS, architectures, and formats of each archive in .audio-soko-kun/config.json. Place the file in the same .audio-soko-kun folder as the images.

{
  "name": "Simple Pitch Shift",
  "category": "effect",
  "assets": [
    {
      "pattern": "simple-pitchshift-*-windows-x64.zip",
      "os": "windows",
      "arch": ["x86_64"],
      "formats": ["vst3", "clap"]
    }
  ]
}
  • name: The display name, from 1 to 60 characters. Without it, this platform shows the repository name.
  • category: One of instrument, effect, analyzer, midi, and utility. This platform uses it only when it cannot infer the category from the bundles.
  • assets: Up to 20 declarations of archives. pattern matches the archive name, where * matches any text. os is one of windows, macos, and linux. arch is an array of x86_64, x86, and arm64. formats is an array of vst3, clap, lv2, and au.

All fields are optional. This platform takes the formats, OS, and architectures from the inspected bundles, and uses the declarations only to check them and to choose the archives to guide.

With assets, this platform guides users only to the archives that match a pattern. It does not list a release whose file is invalid, whose archives match no pattern, or whose inspected archives disagree with the declarations.

This platform reads the file at the tag of each new release, so publish a new release after you change the file.

Updating and withdrawing

To update a listing, publish a new release on GitHub. This platform picks it up automatically and lists it after it passes the checks. This platform also updates the summary from the repository description.

If a new release is not listed, ask your AI agent to check it with list_my_plugins. The agent shows the reason and how to fix it.

To withdraw a listing, make the repository private or delete it, or send a request as described on the Report page.

Renaming or transferring the repository

This platform follows the repository by its GitHub ID, so you do not need to do anything when you rename the repository. The listing moves to the new name within 15 minutes, and links to the old name redirect to the new one.

Do not create another repository with the old name. This platform keeps the old name for the renamed plugin and does not register another repository under it.

If you transfer the repository to another account or organization, the listed release stays listed, and an administrator reviews the next release before listing it.

To change the display name, change name in .audio-soko-kun/config.json and publish a new release.