Skip to main content

Plugins

Plugins are self-contained bundles that extend your agents with skills, sub-agents, hooks, rules, commands, and MCP servers. Package related capabilities into a single installable unit and distribute them to Cursor, Claude, GitHub Copilot, and Codex through a marketplace.

What you can do here​

  • Create, edit, and delete plugins
  • Compose plugins from skills, toolkits, commands, rules, hooks, sub-agents, and MCP servers
  • Target specific marketplace platforms per plugin
  • Preview the generated file structure before publishing
  • Download a plugin as a zip for Cursor or Claude
  • Sync plugins to GitHub via Managed Marketplace Sync or your own GitHub Integration

Create a plugin​

  1. Click Add Plugin.
  2. Enter a Name, Description, and Slug.
  3. Optionally check Publish to set the plugin to active immediately (otherwise it starts as draft).
  4. Click Create — you are taken to the edit page.

Edit a plugin​

The edit page has two columns: the component editor on the left and a Marketplace Preview tree on the right that shows the file structure that will be generated.

Plugin details​

At the top you can change the plugin Name and Description. The Slug is set at creation time and cannot be changed.

Target platforms​

By default a plugin inherits the organization-level marketplace platforms. Toggle Override defaults to choose a custom set of platforms (Cursor, Claude, GitHub Copilot, Codex) for this specific plugin.

Adding components​

Below the details card you will find collapsible sections for each component type. Each section lets you search, add (+), or remove (−) items from the plugin:

ComponentWhat it provides
SkillsMarkdown-based knowledge files with optional scripts, references, and assets
ToolkitsCurated selections of tools from your MCP servers, plus prompts and resources
CommandsSlash-commands (e.g. /deploy) with typed arguments
RulesAlways-apply or glob-scoped rules (.mdc files) that guide agent behavior
HooksEvent-driven automations triggered on agent events (e.g. on_save, on_commit)
Sub-AgentsDedicated agents with their own model, scope, and tool permissions
MCP ServersExisting integrations from your organization's MCP server list

You can also expand Custom MCP Servers at the bottom to paste raw MCP server JSON (stdio, docker, etc.) that will be included in the plugin's .mcp.json.

Marketplace preview​

The right-side panel shows a live file tree of the plugin as it would appear in the marketplace repository:

plugins/<plugin-slug>/
├── skills/
│   └── <skill-slug>/
│       └── SKILL.md
├── commands/
│   └── <command-slug>.md
├── rules/
│   └── <rule-slug>.mdc
├── hooks/
│   └── hooks.json
├── agents/
│   └── <agent-slug>.md
└── .mcp.json

Download a plugin​

From the edit page, click Download Cursor or Download Claude to get a zip file formatted for the respective platform. This is useful for local testing before publishing to the marketplace.

Plugin settings​

Navigate to Plugins → Plugins Settings (or click the gear icon on the plugins list page) to configure organization-wide plugin behavior.

Sync options​

Control whether a wrapper plugin is automatically created when you add certain entities:

  • MCP Servers — creating an MCP server also creates a plugin that wraps it.
  • Toolkits — creating an organization-level toolkit also creates a plugin.
  • Skills — creating an organization-level skill also creates a plugin.

Auto-created plugins stay in sync (rename, delete) with their underlying entity.

Target marketplace platforms​

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

GitHub sync​

Two sync mechanisms are available and can run side by side:

  • Managed (Webrix-hosted) — a private GitHub repo maintained by Webrix. See Managed Marketplace Sync for details.
  • Custom (your GitHub) — your own GitHub Integration with configurable sync modes, branches, and webhooks.

Publishing​

A plugin must have status: active to appear in the marketplace. Draft plugins are only visible in the admin UI.

Only organization-level plugins (no owner_id) are published. User-owned (personal) plugins remain private.

Installing the marketplace in your agents​

Once your plugins are synced to GitHub, follow the platform-specific guide to make them available to your developers:

Tips​

  • Wrap stand-alone MCP servers, skills, or toolkits in a plugin if you want them distributed via the marketplace.
  • Use the marketplace preview to verify the file structure before syncing.
  • Enable auto-create in Plugin Settings to avoid manually wrapping every new entity.