Can I use Appetize as a CLI?

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

Can I expose Appetize through MCP?

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

Where are Appetize credentials stored?

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

Can I deny write access for Appetize MCP tools?

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

productivity

Appetize CLI for AI Agents

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

Appetize CLI Setup

Appetize can be configured headlessly with `kosmokrator integrations:configure appetize`.

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 appetize --set api_key="$APPETIZE_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor appetize --json
kosmokrator integrations:status --json

Credentials

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

Key	Env var	Type	Required	Label
`api_key`	`APPETIZE_API_KEY`	Secret `secret`	yes	API Key
`url`	`APPETIZE_URL`	Text `text`	no	API URL

Command Patterns

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

Generic CLI call

kosmo integrations:call appetize.appetize_list_apps '{}' --json

Provider shortcut

kosmo integrations:appetize appetize_list_apps '{}' --json

Discovery

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

Discovery commands

kosmo integrations:docs appetize --json
kosmo integrations:docs appetize.appetize_list_apps --json
kosmo integrations:schema appetize.appetize_list_apps --json
kosmo integrations:search "Appetize" --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.

`appetize.appetize_list_apps`

List Appetize apps with pagination.

Read read

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_list_apps '{}' --json

Shortcut

kosmo integrations:appetize appetize_list_apps '{}' --json

`appetize.appetize_list_all_apps`

List all Appetize apps without pagination.

Read read

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_list_all_apps '{}' --json

Shortcut

kosmo integrations:appetize appetize_list_all_apps '{}' --json

`appetize.appetize_get_app`

Get one app or app group by public key.

Read read

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_get_app '{}' --json

Shortcut

kosmo integrations:appetize appetize_get_app '{}' --json

`appetize.appetize_create_app`

Create a new Appetize app from a public URL.

Write write

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_create_app '{}' --json

Shortcut

kosmo integrations:appetize appetize_create_app '{}' --json

`appetize.appetize_update_app`

Update an app build or settings.

Write write

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_update_app '{}' --json

Shortcut

kosmo integrations:appetize appetize_update_app '{}' --json

`appetize.appetize_delete_app`

Delete one Appetize app.

Write write

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_delete_app '{}' --json

Shortcut

kosmo integrations:appetize appetize_delete_app '{}' --json

`appetize.appetize_get_usage_summary`

Get account usage summary.

Read read

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_get_usage_summary '{}' --json

Shortcut

kosmo integrations:appetize appetize_get_usage_summary '{}' --json

`appetize.appetize_list_devices`

List supported Appetize devices and OS versions.

Read read

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_list_devices '{}' --json

Shortcut

kosmo integrations:appetize appetize_list_devices '{}' --json

`appetize.appetize_api_get`

Call a safe relative Appetize GET path.

Read read

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_api_get '{}' --json

Shortcut

kosmo integrations:appetize appetize_api_get '{}' --json

`appetize.appetize_api_post`

Call a safe relative Appetize POST path.

Write write

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_api_post '{}' --json

Shortcut

kosmo integrations:appetize appetize_api_post '{}' --json

`appetize.appetize_api_delete`

Call a safe relative Appetize DELETE path.

Write write

Parameters: none

Generic call

kosmo integrations:call appetize.appetize_api_delete '{}' --json

Shortcut

kosmo integrations:appetize appetize_api_delete '{}' --json

Function Schemas

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

appetize.appetize_list_apps 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_list_apps --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_list_all_apps 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_list_all_apps --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_get_app 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_get_app --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_create_app 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_create_app --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_update_app 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_update_app --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_delete_app 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_delete_app --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_get_usage_summary 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_get_usage_summary --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_list_devices 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_list_devices --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_api_get 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_api_get --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_api_post 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_api_post --json

Parameter	Type	Required	Description
No parameters.

appetize.appetize_api_delete 0 parameters

Schema command

kosmo integrations:schema appetize.appetize_api_delete --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.