CloudBees Unify MCP Server

Run workflows, flip feature flags and review security findings in CloudBees Unify.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the CloudBees Unify MCP Server connector does

The CloudBees Unify MCP server connects CloudBees Unify, a DevSecOps platform, to Claude. Its 110 listed tools inspect components and CI controllers, trigger and approve workflows, manage feature flags and targeting, and review security findings and policies. The directory's URL opts into every toolset. Sign-in is the same OAuth as the Unify web app, and your roles limit every call.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

CloudBees Unify MCP Server tools (110)

  • actions_list
  • automation_approve_manual_gate
  • automation_jobs_list
  • automation_pending_tasks_list
  • automation_reject_manual_gate
  • automation_rerun
  • automation_stop
  • automation_trigger_by_branch
  • branches_list
  • controllers_data_get
  • controllers_list
  • endpoint_add
  • endpoint_list
  • extensions_list
  • flag_approval_requests_list
  • flag_configuration_conditions_set
  • flag_configuration_get
  • flag_custom_properties_add
  • flag_custom_properties_delete
  • flag_custom_properties_flag_usage_per_environment
  • flag_custom_properties_list
  • flag_custom_properties_target_group_usage
  • flag_serve_to_target_group
  • flag_target_groups_add
  • flag_target_groups_delete
  • flag_target_groups_flag_usage_per_environment
  • flag_target_groups_list
  • flag_target_groups_list_with_flags_usage
  • flag_target_groups_target_group_usage
  • flags_add
  • flags_applications_list
  • flags_configuration_state_update
  • flags_configurations_list
  • flags_delete
  • flags_environments_list
  • flags_flag_usage_per_environment
  • flags_list
  • flags_sdk_key_get
  • flags_update_defaultValue
  • list_toolsets
  • logs_list
  • organizations_create
  • organizations_get
  • organizations_list
  • organizations_list_suborganizations
  • organizations_search
  • organizations_suborg_report
  • policies_create
  • policies_delete
  • policies_discover
  • policies_get
  • policies_get_schema
  • policies_list
  • policies_run_evaluations_list
  • policies_update
  • properties_add
  • properties_get
  • properties_list
  • property_delete
  • rbac_authorization_check_bulk
  • rbac_authorization_create
  • rbac_authorizations_list
  • rbac_permissions_list
  • rbac_role_create
  • rbac_role_delete
  • rbac_roles_list
  • report_drilldown_get
  • repositories_list
  • resources_get
  • resources_list
  • runs_list
  • scm_branches_list
  • search_resources
  • search_runs
  • security_configuration_get
  • security_configuration_hierarchy_get
  • security_configuration_set
  • security_filter_tools_list
  • security_filters_list
  • security_findings_summary_get
  • security_implicit_scans_set
  • security_issues_all_get
  • security_issues_open_get
  • security_plugin_config_get
  • security_sla_configuration_get
  • security_sla_configuration_remove
  • security_sla_configuration_set
  • security_tenant_sla_configuration_remove
  • services_add
  • services_delete
  • services_list
  • teams_create
  • teams_delete
  • teams_get
  • teams_get_by_id
  • teams_invite_create
  • teams_invite_delete
  • teams_invites_list
  • teams_members_add
  • teams_members_remove
  • teams_memberships_list
  • user_whoami
  • users_get
  • users_get_by_id
  • users_list
  • workflow_get_content
  • workflow_list
  • workflow_schema_get
  • workflow_update_content
  • workflow_validate

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The directory URL is the widest setting. It enables every toolset, including deletes, role changes and security configuration. Use a filtered custom URL to narrow it.
  • Too many tools at once. CloudBees recommends no more than two toolsets at a time.
  • No dynamic client registration. Clients must use the pre-registered public-mcp-client ID.
  • Rate limits apply to many concurrent tool calls from one user; CloudBees publishes no number.
  • Secrets can surface. flags_sdk_key_get returns an SDK key into the conversation.
  • Security claim is the vendor's. CloudBees states the service follows practices covered by its SOC 2 certification; we have not reviewed that report.
  • We could not read tool schemas or annotations. Tool names come from Anthropic's directory; toolsets and behaviour come from CloudBees' documentation.

Frequently asked questions

How do I limit which CloudBees Unify tools Claude can use?

Add CloudBees Unify as a custom connector with a filtered URL instead of the directory listing. CloudBees documents a toolset parameter that serves only the toolsets you name, and a readonly parameter that strips write tools from them. Without any filter the server serves only its read-only default toolset. CloudBees advises enabling no more than two toolsets at a time, and reconnecting after any change.

Why do CloudBees Unify tool calls return permission denied?

Because your role lacks permission for that resource. CloudBees shows every tool to every signed-in user but enforces role-based access on each resource, so a visible tool can still fail. Ask the agent who you are in CloudBees Unify to confirm the organization, check your roles in your user profile, and ask an admin for more roles or team membership if needed.

Why can't I see the data I expect after signing in to CloudBees Unify?

Usually because you picked the wrong organization at sign-in. CloudBees asks you to choose a Root Organization during OAuth, and you only see organizations you can access. Disconnect, reconnect and select the right one. If access was revoked after you authenticated, the same symptom appears, and an admin has to restore your access before the connector can see that data again.

Does CloudBees Unify MCP need an API token?

No. CloudBees says the remote server uses the same sign-in as the web interface, through Google, GitHub or SSO, and no separate MCP credential is needed. Custom setups must use the OAuth client ID public-mcp-client exactly, because dynamic client registration is not supported yet. CloudBees deprecated the local stdio server on May 31, 2026, in favour of the remote one.

Sources

Use it in an agent

Put CloudBees Unify MCP Server to work.

Connect CloudBees Unify MCP Server once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.