Ship AI-written code faster and safer with CloudBees, right from your coding agent.
AI agents write code faster than teams can test, release, and govern it. This plugin brings CloudBees Unify into the coding agent you already use, so the agent that writes your code can also help you test, ship, and govern it:
- Build at AI speed: find out why a build failed, read its logs, and see which test suites and cases broke.
- Jenkins visibility (CloudBees CI): list your controllers and surface disabled or out-of-date plugins and open vulnerabilities.
- Faster, safer releases: trigger, rerun, or stop workflows, approve manual gates, and toggle or progressively roll out feature flags by target group.
- Govern the software factory: review policy gate outcomes for each run, manage policies and approvals, and triage security findings against SLAs, all in one place.
The plugin connects to the Unify MCP server and adds skills for common tasks like onboarding a repository.
Install from the Claude Code marketplace (once published):
/plugin marketplace add cloudbees-oss/cloudbees-unify-ai-plugin
/plugin install cloudbees-unify@unify-ai-plugins
Or install locally from a clone:
git clone https://github.com/cloudbees-oss/cloudbees-unify-ai-plugin.git
claude plugin marketplace add ./cloudbees-unify-ai-plugin
claude plugin install cloudbees-unify@unify-ai-plugins
Once installed, open Claude and connect to Unify using the Unify MCP Server:
- Send the
/mcpcommand to Claude. - Select the
unify-mcp-serverserver - Choose the Authenticate option and follow the instructions in Claude
The desktop app uses the same marketplace. Add cloudbees-oss/cloudbees-unify-ai-plugin
as a plugin marketplace in the app, then install cloudbees-unify.
codex plugin marketplace add cloudbees-oss/cloudbees-unify-ai-plugin
codex plugin add cloudbees-unify@unify-ai-plugins
From a clone, pass the local path to codex plugin marketplace add instead.
Run codex plugin list to confirm the plugin is installed and enabled.
Then sign in to the Unify MCP server:
codex mcp login unify-mcp-server
An MCP server named unify-mcp-server in your own Codex configuration takes
precedence over the plugin's server. Remove it with
codex mcp remove unify-mcp-server to use the plugin's connection.
The Codex app shares its plugin configuration with Codex CLI. Install the plugin with the commands above, or add the same marketplace from the app's plugin settings.
Recommended: Install as an Agent Plugin in VS Code 1.99+ (Copilot Chat agent mode):
-
Open the Extensions view (⇧⌘X) and search for
@agentPlugins. -
If published, search for
cloudbees-unifyand click Install. -
To install from source, run Chat: Install Plugin From Source from the Command Palette and enter:
https://github.com/cloudbees-oss/cloudbees-unify-ai-plugin.git -
The plugin will appear in the Agent Plugins - Installed section. Enable it if needed.
Manual (local clone):
- Clone this repo:
git clone https://github.com/cloudbees-oss/cloudbees-unify-ai-plugin.git - Register the plugin in your VS Code
settings.json:"chat.pluginLocations": { "/absolute/path/to/unify-ai-plugin": true }
- Reload VS Code. The plugin will be enabled and its skills, hooks, and MCP servers will be auto-discovered.
Uses the same plugin format as above. See GitHub Copilot CLI plugin reference.
This plugin ships a .claude-plugin/plugin.json (Claude/VS Code compatible) and a .mcp.json that points at the CloudBees Unify MCP server (https://mcp.cloudbees.io/v1/mcp). Codex reads .codex-plugin/plugin.json and .codex-plugin/mcp.json, which points at the same server.
When enabled, VS Code, Claude Code, and Copilot CLI auto-discover:
- Skills (in
skills/) - Hooks (in
hooks/orhooks.json) - MCP servers (from
.mcp.json)
Codex loads the same skills, hooks, and MCP server from .codex-plugin/plugin.json.
On first use, the MCP server opens a browser window for OAuth (Google, GitHub, or SSO). After that, agent tools invoke Unify transparently.
After installing and enabling the plugin, just ask in plain English. Claude Code, Copilot Chat, or Copilot CLI will route your request through the appropriate skill.
What components are in my CloudBees Unify org?
Show me the latest build status for the checkout-service component.
Are there any open critical security findings this week?
List feature flags for the storefront application.
Why did the last workflow run on payments-api fail? Show me the logs.
The first command in a session opens a browser for OAuth (Google / GitHub / SSO). After that, calls run silently.
Skills are addressable as /cloudbees-unify:list-components:
/cloudbees-unify:list-components
/cloudbees-unify:list-components organization=platform-eng filter=api
The point of running this in Claude Code or Copilot Chat is mixing Unify data with code:
Find the component that owns this repo in Unify, then show me the last 5 builds
and open a diff between the last green commit and HEAD.
A Snyk finding flagged lodash in the auth-service. Pull the finding from Unify,
then update package.json and the lockfile to the patched version.
.claude-plugin/— Claude plugin.json + marketplace.json.codex-plugin/— Codex plugin.json + mcp.json.agents/plugins/— Codex marketplace.json.mcp.json— Unify MCP server config (auto-wired on install)skills/— skill definitionshooks/— SessionStart hook + system prompt injected on session start
See CONTRIBUTING.md for how to add skills.
- If the plugin does not appear after installation, check that the
namefield inplugin.jsonuses only lowercase letters, numbers, and hyphens. - If skills do not load, ensure the skill directory and
SKILL.mdfrontmatter use plain kebab-case names. - If you see an OAuth prompt, this is expected on first use.
- For more, see the Agent Plugins for VS Code documentation.
MIT — see LICENSE.