Submit a plugin
Plugins you can submit
This platform lists OBS Studio plugins whose author administers the GitHub repository and submits it. Check that your repository meets all of the following conditions before submitting.
- The repository is public on GitHub and is not archived.
- GitHub detects a license for the repository. Add a LICENSE file if GitHub shows no license.
- The CMakeLists.txt at the root of the repository references libobs, for example with find_package(libobs), and the repository contains C or C++ sources.
- The latest release on GitHub has the plugin files attached. GitHub records a SHA-256 digest for files uploaded to a release, and this platform uses that digest for checks.
How to submit
Connect your MCP client to https://soko-kun.allegromoltov.jp/mcp. In Claude Code, run:
claude mcp add --transport http plugin-soko-kun https://soko-kun.allegromoltov.jp/mcpSign in with your GitHub account from the MCP client. In Claude Code, run /mcp and choose plugin-soko-kun. In Codex, connect with codex mcp add plugin-soko-kun --url https://soko-kun.allegromoltov.jp/mcp, then sign in with codex mcp login 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 OBS plugin in https://github.com/<owner>/<repository>". You can also tell the agent the category, such as audio filter or dock.
After submitting
This platform registers the plugin as waiting for checks and checks each file against MalwareBazaar, a database of known malware samples, every 15 minutes. Checks for a plugin usually finish within a few hours, so check the plugin page later.
When all files pass the checks, this platform lists the plugin automatically. When you publish a new release on GitHub, this platform finds it and checks it, and keeps listing the previous release until the checks finish.
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: Add a LICENSE file that GitHub can detect.
- not_obs_plugin: Make the root CMakeLists.txt reference libobs.
- no_release, no_verifiable_asset: Publish a release with the plugin files attached.
- duplicate: The repository is already registered. Open its page from the search.
- 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.
Logo and description image
Authors can show one logo and one description image. Place the images in the .soko-kun folder of the repository.
.soko-kun/logo.png
.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.
Updating and withdrawing
To update a listing, publish a new release on GitHub. This platform also updates the summary from the repository description.
To withdraw a listing, make the repository private or delete it, or send a request as described on the Report page.