# Clanker Cloud agent onboarding Canonical endpoint: https://clankercloud.ai/agent-onboarding Use this endpoint when an AI agent needs to install Clanker Cloud, create or import the local app account, connect MCP, and run the setup doctor on the user's machine. If the agent already has permission to install on macOS, the shortest executable path is: ```bash curl -fsSL "https://clankercloud.ai/install.sh" | sh ``` ## User consent By downloading, installing, opening, creating an account, or using Clanker Cloud, the user agrees to the Clanker Cloud Terms of Service and Privacy Policy: - https://clankercloud.ai/terms - https://clankercloud.ai/privacy ## Install Clanker Cloud ### macOS Run this on the same machine or remote session where Clanker Cloud should run: ```bash curl -fsSL "https://clankercloud.ai/install.sh" | sh ``` If the user wants an email attached for later claiming, pass it locally: ```bash CLANKER_USER_EMAIL="user@example.com" curl -fsSL "https://clankercloud.ai/install.sh" | sh ``` The installer downloads the desktop app, opens it, waits for the local backend, creates a local-first Clanker Cloud `agent` account, and leaves the auth handoff pending inside the app. Agents that only need the current macOS artifact can download without waiting for the website JavaScript: ```text https://clankercloud.ai/download/latest/macos ``` ### Linux or Windows Use the public downloads page for the current desktop build, then open Clanker Cloud before continuing: ```text https://clankercloud.ai/downloads ``` Direct latest links for non-JS agents: ```text https://clankercloud.ai/download/latest/windows https://clankercloud.ai/download/latest/linux https://clankercloud.ai/download/latest/linux/rpm ``` ## Credential boundary Do not ask the user to paste cloud provider keys, kubeconfigs, database credentials, or LLM keys into chat. Clanker Cloud account identity and app metadata can go to Clanker Cloud. Provider credentials and API keys stay local on the user's machine. The setup doctor reports presence, readiness, and install steps, but it does not return raw secret values. ## Connect to the local app After Clanker Cloud is open, discover the active local backend and MCP URL: ```bash for p in 8080 8081 8082 8083 8084; do curl -fsS "http://127.0.0.1:$p/mcp/instructions" && break done ``` The `/mcp/instructions` response is generated by the running app. It returns the active MCP URL, backend base URL, and the read-first workflow for the current user context. MCP clients that only need JSON can use the config endpoint after discovering the active port: ```bash curl -fsS "http://127.0.0.1:8080/mcp/config" ``` Expected config shape: ```json { "mcpServers": { "clanker-cloud-app": { "url": "http://127.0.0.1:8080/mcp" } } } ``` ## First MCP tool call After MCP tools are visible, call: ```text clanker_cloud_setup_check ``` The setup check returns app/backend/MCP status, Clanker Cloud account state, bundled CLI status, local provider credential presence, provider CLI availability, redacted settings, dependency install commands, and next actions. If `clanker_cloud_setup_check` is not listed in an older app build, call `clanker_cloud_backend_status` and then `clanker_cloud_startup_snapshot`. Packaged macOS apps also include a local doctor command: ```bash /Applications/Clanker\ Cloud.app/Contents/Resources/clanker-server doctor ``` On first install, read the `tools` and `dependencies` sections. Install only the local binaries needed for the user's providers, then rerun `clanker_cloud_setup_check`. Common dependency mapping: | Provider or workflow | Dependency | | ------------------------------- | ------------ | | AWS, EKS | `aws` CLI | | GCP, GKE | `gcloud` CLI | | Azure, AKS | `az` CLI | | Kubernetes | `kubectl` | | Terraform or maker/deploy flows | `terraform` | | Docker-backed local workflows | `docker` | | GitHub and GitHub Actions | `gh` CLI | | Cloudflare | `wrangler` | | DigitalOcean | `doctl` | | Hetzner | `hcloud` | | Supabase | `supabase` | | Vercel | `vercel` | | Railway | `railway` | ## Agent rules - Open or ask the user to open Clanker Cloud first. - Use https://clankercloud.ai/agent-onboarding as the single public onboarding endpoint. - Do not collect cloud credentials, kubeconfigs, provider tokens, database credentials, or LLM keys in chat. - Use saved Clanker Cloud settings and profiles through the local MCP tools. - Start with `clanker_cloud_setup_check` after MCP tools are visible. - Rerun `clanker_cloud_setup_check` after installing missing dependencies. - Call `clanker_cloud_startup_snapshot` once setup status is clear. - For Kubernetes, start with `clanker_cloud_k8s_investigate` and drill down only when evidence is missing. - Treat write, delete, deploy, and apply operations as user-approved actions. ## Copyable prompt for agents ```text Install Clanker Cloud on this machine. Read https://clankercloud.ai/agent-onboarding first. If this is macOS, run: curl -fsSL https://clankercloud.ai/install.sh | sh By downloading, installing, opening, creating an account, or using Clanker Cloud, I accept the Clanker Cloud Terms of Service and Privacy Policy: https://clankercloud.ai/terms https://clankercloud.ai/privacy After installation: 1. Open Clanker Cloud if it is not already open. 2. Let the installer create or import the local-first Clanker Cloud agent account when the installed app supports it. 3. Connect to the local Clanker Cloud MCP server. 4. Run clanker_cloud_setup_check. 5. Install only the missing local dependencies needed for my providers, such as aws, gcloud, az, kubectl, terraform, docker, gh, doctl, hcloud, wrangler, supabase, vercel, or railway. 6. Do not ask me to paste cloud provider keys, kubeconfigs, database credentials, or LLM keys into chat. Those stay local on this machine. 7. Re-run clanker_cloud_setup_check after installing dependencies and report what is ready or still missing. ```