Can I use Cloudways as a CLI?

Yes. KosmoKrator exposes a Cloudways CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Cloudways through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Cloudways tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Cloudways credentials stored?

Cloudways credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Cloudways MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Cloudways CLI for AI Agents

Use the Cloudways CLI from KosmoKrator to call Cloudways tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Cloudways CLI Setup

Cloudways can be configured headlessly with `kosmokrator integrations:configure cloudways`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure cloudways --set access_token="$CLOUDWAYS_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor cloudways --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`CLOUDWAYS_ACCESS_TOKEN`	Secret `secret`	yes	API Key
`url`	`CLOUDWAYS_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call cloudways.cloudways_list_servers '{}' --json

Provider shortcut

kosmo integrations:cloudways cloudways_list_servers '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs cloudways --json
kosmo integrations:docs cloudways.cloudways_list_servers --json
kosmo integrations:schema cloudways.cloudways_list_servers --json
kosmo integrations:search "Cloudways" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`cloudways.cloudways_list_servers`

List all servers in the Cloudways account.

Read read

Parameters: none

Generic call

kosmo integrations:call cloudways.cloudways_list_servers '{}' --json

Shortcut

kosmo integrations:cloudways cloudways_list_servers '{}' --json

`cloudways.cloudways_get_server`

Get details for a specific Cloudways server.

Read read

Parameters: server_id

Generic call

kosmo integrations:call cloudways.cloudways_get_server '{"server_id":1}' --json

Shortcut

kosmo integrations:cloudways cloudways_get_server '{"server_id":1}' --json

`cloudways.cloudways_list_apps`

List all applications across all servers in the Cloudways account.

Read read

Parameters: none

Generic call

kosmo integrations:call cloudways.cloudways_list_apps '{}' --json

Shortcut

kosmo integrations:cloudways cloudways_list_apps '{}' --json

`cloudways.cloudways_get_app`

Get details for a specific Cloudways application.

Read read

Parameters: server_id, app_id

Generic call

kosmo integrations:call cloudways.cloudways_get_app '{"server_id":1,"app_id":1}' --json

Shortcut

kosmo integrations:cloudways cloudways_get_app '{"server_id":1,"app_id":1}' --json

`cloudways.cloudways_list_domains`

List domains for a specific Cloudways application.

Read read

Parameters: server_id, app_id

Generic call

kosmo integrations:call cloudways.cloudways_list_domains '{"server_id":1,"app_id":1}' --json

Shortcut

kosmo integrations:cloudways cloudways_list_domains '{"server_id":1,"app_id":1}' --json

`cloudways.cloudways_list_projects`

List all projects in the Cloudways account.

Read read

Parameters: none

Generic call

kosmo integrations:call cloudways.cloudways_list_projects '{}' --json

Shortcut

kosmo integrations:cloudways cloudways_list_projects '{}' --json

`cloudways.cloudways_get_current_user`

Get the current authenticated Cloudways account information.

Read read

Parameters: none

Generic call

kosmo integrations:call cloudways.cloudways_get_current_user '{}' --json

Shortcut

kosmo integrations:cloudways cloudways_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

cloudways.cloudways_list_servers 0 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_list_servers --json

Parameter	Type	Required	Description
No parameters.

cloudways.cloudways_get_server 1 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_get_server --json

Parameter	Type	Required	Description
`server_id`	integer	yes	The server ID to look up.

cloudways.cloudways_list_apps 0 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_list_apps --json

Parameter	Type	Required	Description
No parameters.

cloudways.cloudways_get_app 2 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_get_app --json

Parameter	Type	Required	Description
`server_id`	integer	yes	The server ID the application belongs to.
`app_id`	integer	yes	The application ID to look up.

cloudways.cloudways_list_domains 2 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_list_domains --json

Parameter	Type	Required	Description
`server_id`	integer	yes	The server ID the application belongs to.
`app_id`	integer	yes	The application ID to list domains for.

cloudways.cloudways_list_projects 0 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_list_projects --json

Parameter	Type	Required	Description
No parameters.

cloudways.cloudways_get_current_user 0 parameters

Schema command

kosmo integrations:schema cloudways.cloudways_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.