Skip to main content

Akuity MCP Server

The Akuity MCP Server lets MCP-compatible AI agents work with the Akuity Platform, Argo CD, Kargo, and Akuity Agents through authenticated, structured tools. An agent can inspect delivery state, investigate problems, and perform permitted operations without relying on screen scraping or custom API integrations.

Early Access

The Akuity MCP Server is available for selected organizations. Ask your Akuity representative to enable it for your organization.

note

This section describes the MCP server that the Akuity Platform exposes to your AI agents. To connect your own MCP servers as tools for Akuity Agents, see Custom MCP Servers instead.

Capabilities​

The Akuity MCP Server exposes software-delivery capabilities across four areas. The exact tools available depend on the endpoint and the caller's permissions. See the tool reference for the complete list.

AreaWhat an agent can do
Akuity PlatformManage Argo CD and Kargo instances and review fleet-wide delivery, image, vulnerability, and timeline information.
Argo CDInspect applications and Kubernetes resources, troubleshoot delivery issues, and perform permitted operations.
KargoInspect projects, stages, freight, and promotions, and promote releases through the existing delivery process.
Akuity AgentsDelegate incident or promotion analysis, follow the investigation, and manage approval requests.

Connection options​

Akuity Platform users should use the platform endpoint. It provides one authenticated connection to organization resources, fleet insights, and every MCP-enabled Argo CD or Kargo instance the caller has permission to access.

A direct endpoint is an optional, instance-scoped connection for users who authenticate directly with an Argo CD or Kargo instance instead of through the Akuity Platform.

Platform endpointDirect endpoint
Endpointhttps://akuity.cloud/mcp, or https://eu.akuity.cloud/mcp for EU organizationshttps://<ARGO_CD_HOSTNAME>/mcp or https://<KARGO_HOSTNAME>/mcp
Intended forAkuity Platform users and automation.Instance-only users who authenticate directly with one Argo CD or Kargo instance.
AuthorizationAkuity organization roles or a scoped API key.The instance's existing SSO, username/password login, or native token and RBAC.
ScopeOrganization resources, fleet insights, and MCP-enabled Argo CD and Kargo instances.Resources and actions inside that instance.

Neither endpoint grants additional access. The platform endpoint adds organization and fleet capabilities, while a direct endpoint remains limited to one instance. Which tools an agent may call is also capped by the organization's guardrail level.

Before you begin​

The following permissions control who can enable access:

  • Enabling the platform endpoint requires Organization Owner access or a custom role with Organization update permission.
  • Enabling MCP access for an Argo CD or Kargo instance requires update permission on that instance. Organization Owner access is not required.
  • Changing the guardrail level requires the same Organization update permission as the platform endpoint.

Interactive sign-in uses a standard OAuth authorization code flow with PKCE. On the platform endpoint, native clients can use any loopback callback port, and hosted clients (for example Claude.ai) or custom-scheme clients (for example Cursor) are supported after a one-time consent screen. Automation can use an Akuity API key instead of interactive sign-in. Claude.ai, Claude Desktop, and Cowork connect through a custom connector. See Connect MCP clients.

In this section​