Build your first extension
Start with one useful capability. Choose a type, adapt a starter, and upload it to Creator Center.
Declare supported platforms
To publish, extension.json must declare a non-empty supportedHosts array containing web, desktop, or both. These values identify the product host: the desktop app remains desktop even when Electron renders its interface in a browser engine. Each MCP or Skill contribution may narrow supportedHosts to a subset of the extension’s platforms; omitting it inherits the top-level declaration. Every MCP listed in a Skill’s requiresMcp must be available on every platform that Skill supports. Web and Desktop each select the latest published release compatible with their own host, so they may use different versions.
From idea to publication
- 1Choose a Skill or MCP service
- 2Download a starter and customize it
- 3Validate your content and service, then upload for package checks
- 4Set up your publisher identity and submit for review
Local development: current support
The client currently installs published marketplace extensions; importing a local extension package is not yet available. Validate your service with MCP development tools and review Skill instructions and example outputs first. Website checks validate package format, not execution in PrivateBot. Do not publish an unverified extension just to debug it.