Install on macOS
Agents with user approval can run the public installer directly; it installs and opens the app but does not call protected local endpoints.
curl -fsSL "https://clankercloud.ai/install.sh" | shMCP setup
Connect an agent to Clanker Cloud
Open Clanker Cloud on the machine that already has the cloud credentials, kubeconfigs, GitHub context, and provider settings you want the agent to use. The app exposes a local MCP server on one of the app ports.
In the desktop Settings UI, copy the full per-launch authenticated MCP client configuration. It contains the current port and a rotating local capability; an endpoint URL by itself is not authorized.
Give the agent the authenticated per-launch client configuration, not cloud credentials, a bare localhost URL, or a public MCP bridge.
Copy for agents
Use the authenticated desktop client configuration
Direct macOS download
Agents that only need the current artifact can use this redirect without waiting for page JavaScript.
https://clankercloud.ai/download/latest/macosAuthenticated client configuration
Open Clanker Cloud Settings > MCP Server and choose Copy Client Config. Use the whole value, keep it out of chat and source control, and copy a fresh one after restart.
Clanker Cloud Settings > MCP Server > Copy Client ConfigLocal only
The app-hosted MCP endpoint lives on localhost ports 8080 through 8084 and points to the running desktop backend.
Per-launch authentication
Settings > MCP Server > Copy Client Config includes the active port and rotating local capability required by the server.
No bare discovery
Unauthenticated calls to MCP configuration, instructions, and setup-doctor routes are intentionally rejected.
No secrets in chat
Agents should use saved Clanker Cloud settings and local profiles instead of asking the user to paste credentials.
Supported providers
Works across the environments teams already run
The current product positioning covers cloud providers, Kubernetes, GitHub, and bring-your-own AI keys from one local operating surface.
Supports ->AWSGCPAzureOracle CloudTencent CloudKubernetesCloudflareHetznerDigitalOceanVercelGitHubBYOK
Agent workflow
What the agent should do after connecting
Confirm tools
Reload the MCP client and confirm the clanker-cloud-app tools are visible before answering.
Check account state
Call clanker_cloud_account_status first. If no account is ready and the user asked you to install/use Clanker Cloud, call clanker_cloud_create_account.
Run setup check
Call clanker_cloud_setup_check for app, account, provider credential presence, local tools, dependency install commands, redacted settings, and next actions.
Use hosted LLM by default
Hosted Clanker Cloud LLM is the agent default after account login/account creation. Call clanker_cloud_configure_llm with provider clanker-cloud and test true when you need to verify it.
Install needed dependencies
Install only the missing provider CLIs the user needs, such as aws, gcloud, az, kubectl, terraform, gh, wrangler, doctl, or hcloud, then rerun setup check.
Start scanning and wait
Call clanker_cloud_start_scan once setup status is clear and wait for it to finish. Use mode headless for a fresh backend scan, or mode ui when the user wants the visible app to repaint.
Run research and security
Call clanker_cloud_deep_research for estate-wide findings and clanker_cloud_security_scan for exposure, auth gap, credential leak, and misconfiguration findings only after the scan returns.
Use high-level K8s tools
For cluster work, start with clanker_cloud_k8s_investigate and only drill into narrower tools when evidence is missing.
Stay read-first
Treat write, delete, deploy, and apply operations as user-approved actions with an explanation before the call.
Local endpoints
Routes exposed by the running app
| Route | Purpose | When to use it |
|---|---|---|
| /mcp/instructions | Authenticated bootstrap instructions with the active MCP URL and workflow. | Access only after supplying the per-launch capability copied from the desktop UI. |
| /mcp/config | Authenticated JSON MCP server configuration for the active app port. | Access only after supplying the per-launch capability; do not publish the result. |
| /mcp | Authenticated Streamable HTTP MCP transport. | Configure the MCP client with the full copied configuration, not the URL alone. |
| /api/ping | Backend liveness check. | Use only to confirm the app backend is reachable. |
Reference
Read the details behind the setup
MCP infrastructure Q&A
The previous MCP product page now lives here for deeper positioning and FAQ.
Local credentials boundary
How credentials, model-provider payloads, logs, telemetry, BYOK, and MCP localhost access are bounded.
Claude Code MCP example
A concrete app-first workflow for giving an agent live Kubernetes context.
FAQ
Common questions
Is clankercloud.ai/mcp itself the MCP server?
No. This page is the public setup guide. The actual MCP server is exposed locally by the running Clanker Cloud desktop app at http://127.0.0.1:<port>/mcp.
What should I tell Codex or another agent?
Open Settings > MCP Server in the running desktop app and copy the full per-launch client configuration into the MCP client. Do not send the embedded capability through chat or store it in source control.
Does the agent need cloud credentials pasted into chat?
No. The agent should use the local Clanker Cloud MCP tools and the saved settings or profiles already available to the app.
Next step
Ready to connect an agent?
Open the desktop app first, then copy its authenticated per-launch MCP client configuration into the agent running on the same machine or remote session.