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.

productivity

Linode CLI for Cron Jobs

Use the Linode CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write Bearer token auth

Submit Linode feedback View package source

Linode CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Linode CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Linode CLI for Cron Jobs
kosmokrator integrations:configure linode --set access_token="$LINODE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call linode.linode_list_instances '{"page":1,"per_page":1}' --json

Discovery Before Execution

Agents and scripts can inspect Linode docs and schemas before choosing a function.

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

Useful Linode CLI Functions

Function	Type	Parameters	Description
`linode.linode_list_instances`	Read	page, per_page	List all Linode instances (virtual machines) in the account. Returns IDs, labels, status, type, region, and IP addresses.
`linode.linode_get_instance`	Read	id	Get details for a specific Linode instance by ID. Returns full instance information including specs, networking, and disk config.
`linode.linode_list_volumes`	Read	page, per_page	List all block storage volumes in the Linode account. Returns IDs, labels, size, status, and attached Linode info.
`linode.linode_list_domains`	Read	page, per_page	List all DNS domains managed in the Linode account. Returns domain IDs, names, status, and SOA records.
`linode.linode_get_domain`	Read	id	Get details for a specific DNS domain in Linode, including SOA records, status, and zone information.
`linode.linode_list_stackscripts`	Read	page, per_page	List all StackScripts (reusable deployment scripts) in the Linode account. Returns IDs, labels, descriptions, and deployment counts.
`linode.linode_get_current_user`	Read	none	Get information about the current authenticated Linode user, including username, email, and account status.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Linode CLI Pages

CI Linode CLI for CI. Shell Scripts Linode CLI for shell scripts. Headless Automation Linode CLI for headless automation. Coding Agents Linode CLI for coding agents.