Can I use Hostinger as a CLI?

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

Can I expose Hostinger through MCP?

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

Where are Hostinger credentials stored?

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

Can I deny write access for Hostinger MCP tools?

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

productivity

Hostinger MCP Integration for Codex

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

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

Hostinger MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Hostinger Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__hostinger__hostinger_list_servers`	`hostinger.hostinger_list_servers`	Read	List all VPS servers in the Hostinger account. Returns server IDs, names, status, plan, and IP addresses.
`integration__hostinger__hostinger_get_server`	`hostinger.hostinger_get_server`	Read	Get details for a specific Hostinger VPS server by ID. Returns full server information including IP addresses, plan, and status.
`integration__hostinger__hostinger_list_domains`	`hostinger.hostinger_list_domains`	Read	List all domains in the Hostinger account. Returns domain IDs, names, and status.
`integration__hostinger__hostinger_get_domain`	`hostinger.hostinger_get_domain`	Read	Get details for a specific domain in Hostinger by domain ID. Returns full domain information.
`integration__hostinger__hostinger_list_dns_records`	`hostinger.hostinger_list_dns_records`	Read	List DNS records for a specific domain in Hostinger. Returns all record types (A, AAAA, CNAME, MX, TXT, etc.).
`integration__hostinger__hostinger_list_ssl`	`hostinger.hostinger_list_ssl`	Read	List all SSL certificates in the Hostinger account. Returns certificate details including domain, status, and expiry.
`integration__hostinger__hostinger_get_current_user`	`hostinger.hostinger_get_current_user`	Read	Get information about the current authenticated Hostinger account, including email and user details.

Related Hostinger Pages

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