Can I use Linode as a CLI?

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

Can I expose Linode through MCP?

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

Where are Linode credentials stored?

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

Can I deny write access for Linode MCP tools?

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

data

Linode CLI for AI Agents

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

Linode CLI Setup

Linode can be configured headlessly with `kosmokrator integrations:configure linode`.

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 linode --set access_token="$LINODE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor linode --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`	`LINODE_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`LINODE_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 linode.linode_list_instances '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:linode linode_list_instances '{"page":1,"per_page":1}' --json

Discovery

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

Discovery commands

kosmo integrations:docs linode --json
kosmo integrations:docs linode.linode_list_instances --json
kosmo integrations:schema linode.linode_list_instances --json
kosmo integrations:search "Linode" --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.

`linode.linode_list_instances`

List all Linode instances (virtual machines) in the account. Returns IDs, labels, status, type, region, and IP addresses.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call linode.linode_list_instances '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:linode linode_list_instances '{"page":1,"per_page":1}' --json

`linode.linode_get_instance`

Get details for a specific Linode instance by ID. Returns full instance information including specs, networking, and disk config.

Read read

Parameters: id

Generic call

kosmo integrations:call linode.linode_get_instance '{"id":1}' --json

Shortcut

kosmo integrations:linode linode_get_instance '{"id":1}' --json

`linode.linode_list_volumes`

List all block storage volumes in the Linode account. Returns IDs, labels, size, status, and attached Linode info.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call linode.linode_list_volumes '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:linode linode_list_volumes '{"page":1,"per_page":1}' --json

`linode.linode_list_domains`

List all DNS domains managed in the Linode account. Returns domain IDs, names, status, and SOA records.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call linode.linode_list_domains '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:linode linode_list_domains '{"page":1,"per_page":1}' --json

`linode.linode_get_domain`

Get details for a specific DNS domain in Linode, including SOA records, status, and zone information.

Read read

Parameters: id

Generic call

kosmo integrations:call linode.linode_get_domain '{"id":1}' --json

Shortcut

kosmo integrations:linode linode_get_domain '{"id":1}' --json

`linode.linode_list_stackscripts`

List all StackScripts (reusable deployment scripts) in the Linode account. Returns IDs, labels, descriptions, and deployment counts.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call linode.linode_list_stackscripts '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:linode linode_list_stackscripts '{"page":1,"per_page":1}' --json

`linode.linode_get_current_user`

Get information about the current authenticated Linode user, including username, email, and account status.

Read read

Parameters: none

Generic call

kosmo integrations:call linode.linode_get_current_user '{}' --json

Shortcut

kosmo integrations:linode linode_get_current_user '{}' --json

Function Schemas

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

linode.linode_list_instances 2 parameters

Schema command

kosmo integrations:schema linode.linode_list_instances --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of instances per page (default: 100, max: 500).

linode.linode_get_instance 1 parameters

Schema command

kosmo integrations:schema linode.linode_get_instance --json

Parameter	Type	Required	Description
`id`	integer	yes	The Linode instance ID.

linode.linode_list_volumes 2 parameters

Schema command

kosmo integrations:schema linode.linode_list_volumes --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of volumes per page (default: 100).

linode.linode_list_domains 2 parameters

Schema command

kosmo integrations:schema linode.linode_list_domains --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of domains per page (default: 100).

linode.linode_get_domain 1 parameters

Schema command

kosmo integrations:schema linode.linode_get_domain --json

Parameter	Type	Required	Description
`id`	integer	yes	The domain ID.

linode.linode_list_stackscripts 2 parameters

Schema command

kosmo integrations:schema linode.linode_list_stackscripts --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of StackScripts per page (default: 100).

linode.linode_get_current_user 0 parameters

Schema command

kosmo integrations:schema linode.linode_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.