You can connect AI clients such as Claude Code and Gemini to CloudBees Unify using the Model Context Protocol (MCP). This lets you work with CloudBees Unify conversationally through your AI agent.
What is MCP?
MCP is an open standard that lets AI agents connect to external services. CloudBees Unify supports MCP, so any MCP-compatible AI client can access CloudBees Unify capabilities.
Once connected, your AI agent can perform actions such as:
-
Manage components: create, list, search, and delete components.
-
Work with workflows: list, validate, update, and trigger workflows.
-
Investigate security findings, issues, and security reports.
-
Inspect CI controllers: list controllers and retrieve reports.
-
Manage feature flag configurations.
Common use cases
-
Check build status: "What’s the status of my latest build?" instead of opening the Unify dashboard.
-
Investigate failures: "Show me the logs for build #42" to diagnose issues immediately.
-
Manage workflows: "List all workflows for the payment-service component".
-
Handle security findings: "What security vulnerabilities were found in my last build?".
-
Configure feature flags: "Enable the new-checkout-flow flag for the staging environment".
Who should use MCP?
MCP is designed for technical users who want to integrate AI agents with CloudBees Unify:
-
Developers who want their AI agent to access Unify without manual context copying.
-
Platform and DevOps engineers automating investigations and configuration updates.
-
Security engineers summarizing findings from inside their AI agent.
How to connect
To connect your AI agent to CloudBees Unify:
-
Configure your AI client with the CloudBees Unify MCP endpoint:
https://mcp.cloudbees.io/v1/mcp. -
Authenticate using OAuth (same sign-in as the CloudBees Unify web interface).
-
Select your Root Organization.
-
Start asking questions.
For step-by-step instructions, refer to:
Authentication
When you first connect:
-
Your AI client opens your web browser.
-
Sign in using Google, GitHub, or SSO (same as the CloudBees Unify web interface).
-
Select your Root Organization. You only see organizations you have access to.
-
Your AI client stores your credentials securely.
You don’t need a separate credential for MCP. If you can access CloudBees Unify in your web browser, you can connect your AI agent.
Migrate to the remote server
Earlier versions of the MCP integration used a local server (binary or Docker image) that communicated over the stdio transport. That local server is now deprecated. The current approach uses a CloudBees-hosted remote server that your AI client reaches over HTTPS, no local installation required.
-
As of May 31, 2026, the local server (stdio transport) is deprecated.
-
The remote server requires no binary or Docker image on your machine.
-
New capabilities are only available through the remote server.
Refer to Migrate to the remote CloudBees Unify MCP Server for step-by-step migration guidance.
Available tools
CloudBees Unify provides tools for working with components, workflows, builds, security findings, feature flags, and more.
All tools are visible to authenticated users. Your CloudBees Unify roles determine which resources you can access when using those tools.
Refer to Tool reference for more details.
Security
Your connection to CloudBees Unify is secure:
-
All communication is encrypted.
-
You authenticate using the same OAuth flow as the CloudBees Unify web interface.
-
Your AI agent acts with the same permissions as your user account.
-
All tool calls are logged and attributed to your user account.
CloudBees Unify follows industry-standard security practices covered by the CloudBees SOC2 certification.
For security guidance, refer to Secure your MCP connection.