Use Prompt Switchboard with OpenCode through a public packet without overclaiming a published plugin.
OpenCode already ships an official plugin surface and project-root config model. Prompt
Switchboard now adds a public-bundle-ready OpenCode packet in this repo: MCP config, a
smoke loop, and a plugin scaffold you can publish later without pretending it is already
live.
Public-bundle-ready packet and generic MCP path today, not a verified repo-owned host lane yet
Official surface verified: project config plus npm or local plugins
Current repo claim: public packet shipped, published plugin listing not yet live
Public packet contents
Project-root opencode.jsonc example
Publish-ready plugin package scaffold
Compare-first smoke loop and follow-through map
Truthful install and publication notes
Placement and config
Save the MCP example as a project-root opencode.jsonc in your Prompt
Switchboard clone. If you later publish the plugin package, add it to the OpenCode
plugin array using the official npm plugin flow.
Packable artifact path: run npm run release:host-kits
Official surface exists: OpenCode npm plugin flow
Current repo truth: package scaffold present, npm publish still external
Prompt Switchboard still stays local-first, compare-first, and browser-native. This packet does not turn it into a hosted relay, SDK, or generic automation platform.
Owner-run publish packet
Run npm run release:host-kits and verify the OpenCode packet archive under dist/public-bundles/.
Choose the owner-controlled npm package name and namespace for the OpenCode plugin package.
Publish mcp/integration-kits/public-bundles/opencode-plugin/ to npm.
Install it through the official OpenCode plugin flow and verify one compare-first smoke path.
Only after the package URL and install proof exist should you update public docs to claim Prompt Switchboard is publicly published for OpenCode.