Rudder Plugins are capability packages composed from Skills, MCP servers, Apps, or a combination. Browse Rudder’s curated catalog, enter a public GitHub source accepted by skills add, or import the Codex Plugin folder format. Every path shows an immutable compatibility Preview before installation.

What you will do

Open Hub, discover or import a Plugin, preview what Rudder can use, install it into an Organization, and finish any Agent or MCP setup.

Before you start

Prepare a folder containing .codex-plugin/plugin.json and at least one Skill or supported MCP definition. Do not place credentials in the manifest or MCP configuration; use environment references and finish authentication through Rudder’s Managed MCP settings.

Install and set up

  1. Select Hub in the Primary Rail and open Plugins.
  2. Open one curated Plugin, use URL Import with a public source such as coreyhaines31/marketingskills, or choose Import and then Plugin folder or Plugin ZIP. You can also add a Local marketplace or Pinned GitHub marketplace.
  3. Preview package identity, digest, Skills, MCP definitions, App references, executable Skill files, and unsupported surfaces such as browser extensions, scheduled-task templates, and hooks. Inspection executes nothing.
  4. Resolve any Skill collision explicitly: keep the existing Skill, replace it, or install both by renaming the Plugin copy. Then install the package into the current Organization.
  5. For Skills, choose Add to Agent and select the Agents that should use them.
  6. For MCP definitions, choose Set up, then continue authentication, activation, and Agent access in Managed MCP settings.
  7. Open Local Apps directly from Hub > Plugins. Codex .app.json aliases are preserved but are not executable Rudder Local Apps.
  8. If an active Managed MCP connection exposes an HTML UI resource, open it from the MCP component. Rudder renders it in a network-disabled sandbox.
For curated and URL sources, Rudder resolves the latest stable semantic Release or default branch HEAD to a full commit SHA. The Preview and install use that same immutable snapshot. Rudder never invokes npx, package hooks, or Skill scripts. Marketplace policy is provenance, not installation authority; an INSTALLED_BY_DEFAULT entry still requires an explicit install action.

Check the result

The Plugin detail should show Ready or Setup required with its exact version, source, digest, and component state. A package Skill should appear as a read-only package-managed Organization Skill and only reach the Agents you selected. An MCP connection remains a disabled draft until its normal setup is complete. Use Try in Chat after at least one installed capability is available to the current Organization. For a Skill you want to edit independently, choose Customize. Rudder creates a managed-local Organization Skill copy with provenance; Plugin lifecycle actions no longer change or remove that copy.

Update or roll back

Open the newer Detail Preview before choosing Update. Rudder shows old and new execution surfaces. When the update adds or changes executable Skills or MCP access, confirm the access expansion explicitly. Rudder then prepares its component projections before switching the active installation. If preparation fails, the current version remains active and the Preview can be retried. After a successful update, choose Roll back to reactivate the retained previous immutable package. Rollback does not rewrite either package snapshot. When App Builder produces a new Local App revision, Hub shows Update available. The current revision stays active until you open the Plugin detail and choose Apply update.

Disable or uninstall

Disabling a Plugin removes package capability from new work without deleting the package, external connections, App source, or App data. Re-enabling restores the previous package Skill assignments. Uninstall removes package-owned Skill projections and the active installation. It does not delete user Goals, Automations, Documents, external MCP connections, Local App source, or App business data. You can preview and install the package again later.