Can I use UpCloud as a CLI?

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

Can I expose UpCloud through MCP?

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

Where are UpCloud credentials stored?

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

Can I deny write access for UpCloud MCP tools?

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

productivity

UpCloud MCP Integration for Codex

Connect UpCloud 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 UpCloud feedback View package source

Connect UpCloud 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.

UpCloud MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only UpCloud 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.

UpCloud Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__upcloud__upcloud_list_servers`	`upcloud.upcloud_list_servers`	Read	List all cloud servers on the UpCloud account.
`integration__upcloud__upcloud_get_server`	`upcloud.upcloud_get_server`	Read	Get details for a specific UpCloud server by UUID.
`integration__upcloud__upcloud_list_storages`	`upcloud.upcloud_list_storages`	Read	List storage devices on the UpCloud account. Optionally filter by type (disk, backup, cdrom).
`integration__upcloud__upcloud_list_networks`	`upcloud.upcloud_list_networks`	Read	List private networks on the UpCloud account.
`integration__upcloud__upcloud_list_ips`	`upcloud.upcloud_list_ips`	Read	List IP addresses on the UpCloud account.
`integration__upcloud__upcloud_list_zones`	`upcloud.upcloud_list_zones`	Read	List available UpCloud zones (data centers).
`integration__upcloud__upcloud_get_current_user`	`upcloud.upcloud_get_current_user`	Read	Get the profile of the currently authenticated UpCloud user. Useful for verifying credentials and displaying account information.

Related UpCloud Pages

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