Can I use Kamatera as a CLI?

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

Can I expose Kamatera through MCP?

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

Where are Kamatera credentials stored?

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

Can I deny write access for Kamatera MCP tools?

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

productivity

Kamatera MCP Integration for Codex

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

7 functions 6 read 1 write Bearer token auth

Submit Kamatera feedback View package source

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

Kamatera MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Kamatera Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__kamatera__kamatera_list_servers`	`kamatera.kamatera_list_servers`	Read	List all cloud servers in the Kamatera account. Returns IDs, names, status, and configuration details.
`integration__kamatera__kamatera_get_server`	`kamatera.kamatera_get_server`	Read	Get details for a specific Kamatera cloud server by ID. Returns full server information including status, CPU, RAM, disk, and IP addresses.
`integration__kamatera__kamatera_create_server`	`kamatera.kamatera_create_server`	Write	Create a new cloud server in Kamatera. Requires a name, datacenter, image, CPU count, RAM, and disk size.
`integration__kamatera__kamatera_list_networks`	`kamatera.kamatera_list_networks`	Read	List all networks in the Kamatera account. Returns network IDs, names, datacenter, and CIDR details.
`integration__kamatera__kamatera_list_images`	`kamatera.kamatera_list_images`	Read	List all available images for server creation in Kamatera. Returns image IDs, names, OS type, and sizes.
`integration__kamatera__kamatera_list_datacenters`	`kamatera.kamatera_list_datacenters`	Read	List all available Kamatera datacenter locations. Returns datacenter IDs, names, city, and country.
`integration__kamatera__kamatera_get_current_user`	`kamatera.kamatera_get_current_user`	Read	Get information about the current authenticated Kamatera account, including email, name, and account details.

Related Kamatera Pages

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