Can I use Cloudways as a CLI?

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

Can I expose Cloudways through MCP?

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

Where are Cloudways credentials stored?

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

Can I deny write access for Cloudways MCP tools?

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

productivity

Cloudways MCP Integration for LangChain

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

7 functions 7 read 0 write Bearer token auth

Submit Cloudways feedback View package source

Connect Cloudways to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Cloudways MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Cloudways Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Cloudways integration catalog.

MCP tool	Source function	Type	Description
`integration__cloudways__cloudways_list_servers`	`cloudways.cloudways_list_servers`	Read	List all servers in the Cloudways account.
`integration__cloudways__cloudways_get_server`	`cloudways.cloudways_get_server`	Read	Get details for a specific Cloudways server.
`integration__cloudways__cloudways_list_apps`	`cloudways.cloudways_list_apps`	Read	List all applications across all servers in the Cloudways account.
`integration__cloudways__cloudways_get_app`	`cloudways.cloudways_get_app`	Read	Get details for a specific Cloudways application.
`integration__cloudways__cloudways_list_domains`	`cloudways.cloudways_list_domains`	Read	List domains for a specific Cloudways application.
`integration__cloudways__cloudways_list_projects`	`cloudways.cloudways_list_projects`	Read	List all projects in the Cloudways account.
`integration__cloudways__cloudways_get_current_user`	`cloudways.cloudways_get_current_user`	Read	Get the current authenticated Cloudways account information.

Related Cloudways Pages

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