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 MCP Integration for Codex

Connect Linode to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit Linode feedback View package source

Connect Linode to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Linode MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-linode": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=linode",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=linode --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Linode instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Linode Tools Visible to Codex

Codex sees stable MCP tool names generated from the Linode integration catalog.

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

Related Linode Pages

Linode CLIUse direct JSON commands instead of MCP discovery. Linode MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.