Managed Marketplace Sync

Managed Marketplace Sync lets Webrix host a private GitHub repository on your behalf that always reflects the current state of your organization's plugin marketplace. It is a drop-in alternative to setting up your own GitHub Integration — Webrix handles repository creation, access, and commits so your developers can add the marketplace to Cursor, Claude, GitHub Copilot, and Codex without any DevOps overhead.

Beta feature

Managed Marketplace Sync is currently gated by the managed-marketplace-sync beta flag. Contact Webrix support to enable it for your organization.

What gets synced

The managed repository contains your organization's plugins — their manifests, bundled skills, commands, rules, hooks, sub-agents, and MCP server configuration.

Org-only

Only organization-level plugins (no owner_id, status: active) are published. User-owned (personal) plugins are never included, keeping them private to the authoring user.

Stand-alone MCP servers, skills, and toolkits are not published automatically — wrap them in a plugin if you want them in the marketplace. This keeps the marketplace focused on ready-to-install plugin bundles and avoids surprising dependents when an underlying entity changes.

Repository layout

The repository provisioned by Webrix is a standard marketplace layout that works directly with Cursor, Claude, GitHub Copilot, and Codex:

your-org-slug/
├── .cursor-plugin/
│   └── marketplace.json
├── .claude-plugin/
│   └── marketplace.json
├── .github/plugin/
│   └── marketplace.json
├── .agents/plugins/
│   └── marketplace.json
├── plugins/
│   └── <plugin-slug>/
│       ├── .cursor-plugin/
│       │   └── plugin.json
│       ├── .claude-plugin/
│       │   └── plugin.json
│       ├── .mcp.json
│       └── skills/
│           └── <skill-slug>/
│               └── SKILL.md

Enabling the integration

1. Go to Plugins in your Webrix admin dashboard.
2. In the Managed marketplace sync banner, click Set up.
3. In the dialog:
   • Target marketplace platforms — choose which plugin platforms the managed repository should publish to (Cursor, Claude, GitHub Copilot, Codex). You can change this later.
   • GitHub collaborators — add the GitHub usernames that should receive read-only access to the private repository. Start typing to search GitHub users, or accept the suggested user based on your email.
4. Click Enable managed marketplace sync.

Webrix will then:

• Create a private GitHub repository named after your organization slug in the Webrix-managed GitHub organization.
• Invite each listed collaborator with pull (read-only) access.
• Commit the current marketplace state in a single commit.

Once enabled, the Managed marketplace sync banner becomes a green pill with a link to the generated repository and a Plugins Settings button that opens the dedicated settings page.

Managing the integration

After initial enablement, use the dedicated Plugins Settings page at Plugins → Plugins Settings (/plugins/settings). The page is organized into three sections:

Sync options

These toggles are independent of GitHub — they control whether a matching wrapper plugin is automatically created when you add an MCP server, toolkit, or skill. The auto-created plugin stays in sync with its underlying entity on rename and is removed on delete.

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

Target marketplace platforms

Checkboxes for Cursor, Claude, GitHub Copilot, and Codex. The selected platforms are honored by both the Managed GitHub sync and your own GitHub Integration, so plugin manifests are emitted consistently no matter which sync you use. Saving triggers a full resync on any active GitHub sync so removed platforms stop being published.

GitHub sync

A single section with two expandable rows — each loads its full configuration lazily when you open it:

• Managed (Webrix-hosted) — the Webrix-managed private repository described in the rest of this document. When expanded you see the repo link, push / pull actions, last sync status, collaborator editor, and remove-integration action.
• Custom (your GitHub) — your own GitHub Integration (or Bitbucket), embedded inline. When expanded it shows the full provider configuration with per-entity sync modes, branches, and webhook settings.

Both rows show an at-a-glance status pill (Active / Paused / Not configured / Last sync failed) in the collapsed header so you can see health without expanding.

Automatic sync triggers

The managed repository is kept up-to-date automatically:

Action in Webrix	Triggered sync
Create/update/delete an organization plugin	Publishes the plugin and refreshes manifests
Change target marketplace platforms	Full resync of the repository
Change GitHub collaborators	Reconciles access on the existing repo

All syncs run in the background and produce a single, descriptive commit per change to keep the history clean and easy to audit.

Adding the marketplace to a plugin host

Once the managed repository is populated, share the repository URL with your team and follow the host-specific guide:

• Add the marketplace to Cursor
• Add the marketplace to Claude
• Add the marketplace to Codex
• Add the marketplace to GitHub Copilot

Differences vs. GitHub Integration

Managed Marketplace Sync and the customer-owned GitHub Integration are independent.

Feature	GitHub Integration	Managed Marketplace Sync
Repository ownership	Your GitHub organization	Webrix-managed GitHub organization
What is stored	Full org configuration (toolkits, skills, MCPs, commands, clients)	Marketplace-ready plugin bundles
Two-way sync	Yes (push from Webrix, webhook pulls from GitHub)	No (one-way: Webrix → GitHub)
Access control	Your GitHub organization permissions	Explicit read-only collaborators you manage in Webrix
Setup effort	Create an app + install + configure	One-click
Best for	Version-controlling your Webrix configuration	Distributing plugins to developer tooling

You can run both integrations side-by-side — they write to different repositories and do not interfere with each other.

Troubleshooting

"The managed marketplace GitHub app is not configured"

The Webrix deployment is missing the required MANAGED_MARKETPLACE_GITHUB_* environment variables. Contact your Webrix administrator.

Sync succeeds but a plugin is missing

• Confirm the plugin's status is active and it is not user-owned (no owner_id).
• Confirm the target marketplace platform is enabled on the settings page.
• Stand-alone MCP servers, skills, and toolkits are not synced. Wrap them in a plugin to include them in the marketplace.

Collaborators didn't get an invite

• GitHub usernames must match exactly (the search-as-you-type helper avoids typos).
• New invites arrive by email; check the collaborator's GitHub notifications.
• Removing a user from the list revokes access on the next save.

Last error shown after resync

The "Last sync failed" banner shows the exact error returned from GitHub. Common causes:

• GitHub App installation was removed or rate-limited — Webrix will retry on the next change.
• A collaborator username does not exist or has been renamed.
• Network connectivity between Webrix and GitHub's API.

Clicking Resync now reattempts the full sync and clears the error on success.