Can I use OVHcloud as a CLI?

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

Can I expose OVHcloud through MCP?

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

Where are OVHcloud credentials stored?

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

Can I deny write access for OVHcloud MCP tools?

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

productivity

OVHcloud MCP Integration for Codex

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

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

OVHcloud MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

OVHcloud Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__ovh__ovh_list_servers`	`ovh.ovh_list_servers`	Read	List all dedicated servers in the OVH account. Returns a list of server service names.
`integration__ovh__ovh_get_server`	`ovh.ovh_get_server`	Read	Get details for a specific OVH dedicated server by service name. Returns full server information including hardware, network, and OS details.
`integration__ovh__ovh_list_domains`	`ovh.ovh_list_domains`	Read	List all domains in the OVH account. Returns a list of domain names.
`integration__ovh__ovh_list_vps`	`ovh.ovh_list_vps`	Read	List all VPS instances in the OVH account. Returns a list of VPS service names.
`integration__ovh__ovh_list_ip`	`ovh.ovh_list_ip`	Read	List all IP addresses in the OVH account. Returns a list of IP blocks and addresses.
`integration__ovh__ovh_list_projects`	`ovh.ovh_list_projects`	Read	List all public cloud projects in the OVH account. Returns a list of project IDs.
`integration__ovh__ovh_get_current_user`	`ovh.ovh_get_current_user`	Read	Get information about the current authenticated OVH account, including nichandle, email, and account details.

Related OVHcloud Pages

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