Skip to main content
The Astro Private Cloud (APC) MCP server exposes platform operations and Airflow state to AI agent clients as a governed Model Context Protocol (MCP) tool surface. It is an additional interface to the same platform, subject to the same role-based access control (RBAC) as the APC UI and the Astro CLI, not a new control path.
Astro Private Cloud 2.2This feature was introduced in Astro Private Cloud 2.2. To access this feature, upgrade your Astro Private Cloud installation to 2.2 or later.

​
Availability

The Deployment model and ingress model determine what works on your install. See Connect a client.

​
Connect a client

To check availability, obtain a token, connect VS Code or Cursor, and make your first tool call, see Connect a client to the Astro Private Cloud MCP server.

​
Tool reference

For every tool, its arguments, required permission, and whether it restarts a Deployment, see Astro Private Cloud MCP server tool reference.

​
Skills

For the bundled skills (debugging-dags and migrating-airflow-2-to-3), how to invoke them from a prompt or through load_skill, and which route works in each client, see Astro Private Cloud MCP server skills.

​
Enable and configure the MCP server

To enable, configure, and disable the server through Helm chart values, see Set up and configure the Astro Private Cloud MCP server.

​
Runbook

For what to check when the gate rejects a caller, Laminar is unreachable, or task logs come back empty, plus the error reference and the fast disable path during an incident, see Astro Private Cloud MCP server runbook and error reference.

​
Security posture

For what the agent can reach and as whom, see Astro Private Cloud MCP server security posture.