ASTROSCALE / PUBLIC MCP GUIDE

Agent access,
scoped.

The Astroscale MCP endpoint is https://mcp.astroscale.dev/mcp. It uses Streamable HTTP and accepts OAuth 2.1 or an Astroscale API key.

Authentication

For interactive access, add the endpoint in a compatible MCP client and choose Sign in. The client discovers OAuth metadata, opens Astroscale's Cognito login, and enforces your normal MFA. For automation, issue an expiring API key in Settings and send it as a bearer token. The key must include mcp:access plus the operation scopes it needs; mcp:access alone grants no app, account, or cost access.

Client example

{
  "mcpServers": {
    "astroscale": {
      "url": "https://mcp.astroscale.dev/mcp"
    }
  }
}

Available operations include account and region discovery, application provisioning, deployments, write-only environment management, logs, lifecycle actions, costs, deletion tracing, managed PostgreSQL, and explicitly confirmed destruction. Agents can also update application configuration, switch a hostname, or initiate a Region move after explicit confirmation. They can inspect and explicitly confirm public TCP ingress changes or same-account, same-Region private service routes. Managed PostgreSQL is private to one app and delivers a write-only DATABASE_URL. Public ingress replaces the complete custom rule set; private routes use the fixed internal TCP port 8080. OAuth uses the signed-in user's role; API keys use only their selected scopes.

Inspect edge connectors

Use list_edge_connectors to find a device, then get_edge_connector_overview to read specifications, host utilization with freshness, compatibility, and app reservations. get_edge_connector_history reads seven-day CPU, memory, and root disk history with windows 1h, 24h, or 7d. Missing readings are null; buckets include averages, sampled peaks, and counts. list_edge_connector_activity returns paginated checks, updates, and workload operations with offset and limit (1–100). These reads require apps:read alongside MCP access. Sent to device means delivered, not completed. Existing maintenance tools require their existing permissions and explicit confirmation.

Console-only actions

AWS account onboarding, CodeConnection authorization, GitHub App installation, domain purchase, Stripe billing, team invitations, API-key issuance, and platform administration remain in the console. They require browser consent, payment, or identity controls and are intentionally not agent tools.

Read the full console guide for every console workflow and the repository MCP reference for permissions and operation details.