Skip to content
OpenTeamDocs
DocsAdvanced setup

Build a plugin

Package skills, tools, or both as a plugin to reuse them or share them with others. For instructions only you will use, a private skill is simpler.

On this page

Choose a plugin type

TypeContains
SkillsInstructions and supporting files
Remote MCPA connection to an MCP server over HTTP that your OpenTeam server can reach
Packaged MCPAn MCP server that runs on the bots' computer
Hybrid skills + packaged MCPSkills together with a packaged MCP server

A packaged MCP server must include everything it needs to run. OpenTeam doesn't compile code or install dependencies when it installs a plugin.

Create a plugin

  1. Open Marketplace, then choose Manage → Develop plugins.
  2. Choose a Plugin type, then Create plugin.
  3. In Package definition, set a unique key, a name, a version, and a description.
  4. Edit the definition, including its skills and files, or use Load / reload folder to load them from disk. Then choose Validate and save.

Saving a draft doesn't change any installed copy of the plugin.

Test it

  1. Choose Install for testing.
  2. Set up an account if the plugin needs one, and run a small read with Test a tool under Manage → Accounts and settings.
  3. Try the real workflow in chat.

Check what happens with missing credentials, service errors, and reconnecting. For tools that change data, test with data you don't mind losing.

Write clear tool descriptions and input schemas, since bots rely on them to pick the right tool. Make it clear when a tool changes data or sends information to an external service.

Share it

Choose Export ZIP to package the plugin. Exports never include connected accounts, credentials, so keep secrets in account setup rather than in plugin files.

To release an update, publish the new package with the same key, and raise the version so people can tell releases apart. When the changed package reaches someone's server, for example through a plugin source, they review the changes and choose Apply reviewed update. Plugins in this repository ship with OpenTeam instead: when a server updates, each installed one moves to the newer version automatically and its connected accounts reconnect. Raise the version, or the change won't be applied. Granola and Notion, which fetch their files when installed, and any plugin replaced by an uploaded package, still need a reviewed update.

Reference

The plugin authoring reference covers the directory layout, manifest format, OAuth settings, packaged executables, and how to contribute a plugin to this repository.

View source on GitHub