6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
public-mcp-client ID.flags_sdk_key_get returns an SDK key into the conversation.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.
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.
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.
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.
WWW-Authenticate header naming mcp.cloudbees.io/.well-known/oauth-protected-resource and the scope mcp:unify:connect; the descriptor names id.cloudbees.io as the authorization server (2026-11-18) · retrieved 2026-11-18Connect 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.