Can I use Kamatera as a CLI?

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

Can I expose Kamatera through MCP?

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

Where are Kamatera credentials stored?

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

Can I deny write access for Kamatera MCP tools?

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

productivity

Kamatera CLI for AI Agents

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

Kamatera CLI Setup

Kamatera can be configured headlessly with `kosmokrator integrations:configure kamatera`.

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 kamatera --set access_token="$KAMATERA_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor kamatera --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`	`KAMATERA_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`KAMATERA_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 kamatera.kamatera_list_servers '{}' --json

Provider shortcut

kosmo integrations:kamatera kamatera_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 kamatera --json
kosmo integrations:docs kamatera.kamatera_list_servers --json
kosmo integrations:schema kamatera.kamatera_list_servers --json
kosmo integrations:search "Kamatera" --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.

`kamatera.kamatera_list_servers`

List all cloud servers in the Kamatera account. Returns IDs, names, status, and configuration details.

Read read

Parameters: none

Generic call

kosmo integrations:call kamatera.kamatera_list_servers '{}' --json

Shortcut

kosmo integrations:kamatera kamatera_list_servers '{}' --json

`kamatera.kamatera_get_server`

Get details for a specific Kamatera cloud server by ID. Returns full server information including status, CPU, RAM, disk, and IP addresses.

Read read

Parameters: id

Generic call

kosmo integrations:call kamatera.kamatera_get_server '{"id":"example_id"}' --json

Shortcut

kosmo integrations:kamatera kamatera_get_server '{"id":"example_id"}' --json

`kamatera.kamatera_create_server`

Create a new cloud server in Kamatera. Requires a name, datacenter, image, CPU count, RAM, and disk size.

Write write

Parameters: name, datacenter, image, cpu, ram, disk, password, network, quantity

Generic call

kosmo integrations:call kamatera.kamatera_create_server '{"name":"example_name","datacenter":"example_datacenter","image":"example_image","cpu":1,"ram":1,"disk":1,"password":"example_password","network":"example_network"}' --json

Shortcut

kosmo integrations:kamatera kamatera_create_server '{"name":"example_name","datacenter":"example_datacenter","image":"example_image","cpu":1,"ram":1,"disk":1,"password":"example_password","network":"example_network"}' --json

`kamatera.kamatera_list_networks`

List all networks in the Kamatera account. Returns network IDs, names, datacenter, and CIDR details.

Read read

Parameters: none

Generic call

kosmo integrations:call kamatera.kamatera_list_networks '{}' --json

Shortcut

kosmo integrations:kamatera kamatera_list_networks '{}' --json

`kamatera.kamatera_list_images`

List all available images for server creation in Kamatera. Returns image IDs, names, OS type, and sizes.

Read read

Parameters: none

Generic call

kosmo integrations:call kamatera.kamatera_list_images '{}' --json

Shortcut

kosmo integrations:kamatera kamatera_list_images '{}' --json

`kamatera.kamatera_list_datacenters`

List all available Kamatera datacenter locations. Returns datacenter IDs, names, city, and country.

Read read

Parameters: none

Generic call

kosmo integrations:call kamatera.kamatera_list_datacenters '{}' --json

Shortcut

kosmo integrations:kamatera kamatera_list_datacenters '{}' --json

`kamatera.kamatera_get_current_user`

Get information about the current authenticated Kamatera account, including email, name, and account details.

Read read

Parameters: none

Generic call

kosmo integrations:call kamatera.kamatera_get_current_user '{}' --json

Shortcut

kosmo integrations:kamatera kamatera_get_current_user '{}' --json

Function Schemas

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

kamatera.kamatera_list_servers 0 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_list_servers --json

Parameter	Type	Required	Description
No parameters.

kamatera.kamatera_get_server 1 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_get_server --json

Parameter	Type	Required	Description
`id`	string	yes	The server ID.

kamatera.kamatera_create_server 9 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_create_server --json

Parameter	Type	Required	Description
`name`	string	yes	The server name.
`datacenter`	string	yes	The datacenter ID (e.g. "IL-JER").
`image`	string	yes	The image ID or name for the OS to install.
`cpu`	integer	yes	Number of vCPUs.
`ram`	integer	yes	RAM in MB.
`disk`	integer	yes	Disk size in GB.
`password`	string	no	Root password for the server. Auto-generated if omitted.
`network`	string	no	Network ID to attach the server to.
`quantity`	integer	no	Number of servers to create with this configuration.

kamatera.kamatera_list_networks 0 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_list_networks --json

Parameter	Type	Required	Description
No parameters.

kamatera.kamatera_list_images 0 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_list_images --json

Parameter	Type	Required	Description
No parameters.

kamatera.kamatera_list_datacenters 0 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_list_datacenters --json

Parameter	Type	Required	Description
No parameters.

kamatera.kamatera_get_current_user 0 parameters

Schema command

kosmo integrations:schema kamatera.kamatera_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.