productivity
UpCloud CLI for Headless Automation
Use the UpCloud CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 7 read 0 write Bearer token auth
UpCloud CLI for Headless Automation
Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.
Use headless automation when another tool needs a stable local command surface. The UpCloud CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# UpCloud CLI for Headless Automation
kosmokrator integrations:configure upcloud --set access_token="$UPCLOUD_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call upcloud.upcloud_list_servers '{}' --json Discovery Before Execution
Agents and scripts can inspect UpCloud docs and schemas before choosing a function.
kosmo integrations:docs upcloud --json
kosmo integrations:docs upcloud.upcloud_list_servers --json
kosmo integrations:schema upcloud.upcloud_list_servers --json
kosmo integrations:search "UpCloud" --json
kosmo integrations:list --json Useful UpCloud CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
upcloud.upcloud_list_servers | Read | none | List all cloud servers on the UpCloud account. |
upcloud.upcloud_get_server | Read | uuid | Get details for a specific UpCloud server by UUID. |
upcloud.upcloud_list_storages | Read | type | List storage devices on the UpCloud account. Optionally filter by type (disk, backup, cdrom). |
upcloud.upcloud_list_networks | Read | none | List private networks on the UpCloud account. |
upcloud.upcloud_list_ips | Read | none | List IP addresses on the UpCloud account. |
upcloud.upcloud_list_zones | Read | none | List available UpCloud zones (data centers). |
upcloud.upcloud_get_current_user | Read | none | Get the profile of the currently authenticated UpCloud user. Useful for verifying credentials and displaying account information. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.