Skip to main content

Plugin Settings

Plugin Settings configures organization-wide plugin behavior. Open it by selecting Plugins Settings, or the gear icon, on the Plugins list page.

Plugins Settings page with Marketplace name, Sync options toggles for MCP servers, Toolkits, and Skills, Target marketplace platforms checkboxes, GitHub sync, and Sync from GitHub sections

Marketplace name​

A human-readable identifier used in the install commands generated for end users (for example, /plugin install my-plugin@<marketplace-name>).

Sync options​

Control whether a wrapper plugin is created automatically when you add certain entities. Renaming or deleting the entity updates its plugin.

ToggleEffect
MCP ServersCreating an MCP server also creates a plugin that wraps it.
ToolkitsCreating an organization toolkit also creates a plugin that wraps it.
SkillsCreating an organization skill also creates a plugin that wraps it.

Plugins are created when an entity is published. Drafts are skipped until then, and a skill gets a plugin only after security review allows it. Each enabled row also has Groups with a Choose groups button. Only entities in the groups you choose get a plugin. Leave it empty to include every entity of that type.

Turning a toggle on offers to create plugins for the entities you already have. If you skip it, each enabled row keeps showing how many of them don't have a plugin yet (for example, "3 of 12 MCP servers don't have a plugin yet"). Select that line, or Sync now, to reopen the Create plugins for …? dialog, where a checkbox per entity (and Select all) chooses which ones get a plugin. Unselected entities stay listed so you can add them later. When the plugins are created, Willow pushes them to your connected Git repository in one sync, so the repository gets a single change instead of one per plugin.

Target marketplace platforms​

Select which platforms the organization targets by default: Cursor, Claude, GitHub Copilot, Codex, and OpenCode. Individual plugins can override this from their edit page.

Target marketplace platforms with Cursor, Claude, GitHub Copilot, Codex, and OpenCode selected

OpenCode has no plugin-marketplace concept, so instead of a marketplace.json it receives an OpenCode-native layout (.opencode/skills, .opencode/commands, .opencode/agents, and a root opencode.json for MCP servers). See Adding Your Marketplace to OpenCode.

GitHub sync​

Two mechanisms are available and can run side by side:

Sync from GitHub​

Import plugins from one or more external GitHub repositories, with optional daily auto-sync. See Sync Plugins from GitHub.

Custom install command​

Configure the Custom Plugin Install Command under Settings > End-User Settings. It overrides the install command shown to users with a JSONata expression per platform. See End-User Settings.

The JSONata expression receives an env object with platform, pluginSlug, pluginName, pluginVersion, marketplaceName, and downloadUrl.