This repository provides a prepackaged agent plugin that lets AI coding agents (VS Code Copilot Chat, Claude Code, and Copilot CLI) talk to CloudBees Unify — including components, workflow runs, build status and logs, security findings, feature flags, CI controllers, users, and teams — via the Unify MCP server.
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 install ./cloudbees-unify-ai-plugin --scope user
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
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).
When enabled, VS Code, Claude Code, and Copilot CLI auto-discover:
- Skills (in
skills/) - Hooks (in
hooks/orhooks.json) - MCP servers (from
.mcp.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/— plugin.json + 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.