Clawops
Deploy and lifecycle-manage self-hosted OpenClaw instances on cloud providers through an MCP-driven CLI so your agent handles provisioning—not a spreadsheet of SSH steps.
Overview
clawops is an Operate-phase MCP server that deploys and manages self-hosted OpenClaw instances across clouds via the @clawops/cli mcp serve command.
What is this MCP server?
- MCP mode via @clawops/cli: positional args mcp serve (stdio)
- Deploy and manage self-hosted OpenClaw instances across cloud providers
- npm package @clawops/cli v1.4.0
- GitHub: dfridkin/clawops with documented website URL
- Targets operators who want agent-assisted cloud provisioning for OpenClaw
- @clawops/cli package version 1.4.0
- MCP entry: positional commands mcp + serve (stdio transport)
- Repository: github.com/dfridkin/clawops
Community signal: 1 GitHub stars.
What problem does it solve?
Self-hosting OpenClaw on multiple clouds means repetitive provisioning steps that do not fit cleanly into agent workflows or single-machine dev setups.
Who is it for?
Indie builders standardizing on OpenClaw who self-host on cloud VMs and want agent-driven deploy and ops from Claude Code or Cursor.
Skip if: Teams only using hosted agent SaaS with no OpenClaw footprint, or builders without cloud accounts and infra credentials.
What do I get? / Deliverables
After installing @clawops/cli and registering MCP serve, your agent can drive OpenClaw deploy and management operations on your cloud targets.
- MCP-served Clawops control plane for OpenClaw instances
- Repeatable multi-cloud deploy and management workflows via agent
- Versioned CLI integration (1.4.0) documented on GitHub
Recommended MCP Servers
Journey fit
Operate / infra is canonical because clawops is about running and managing deployed OpenClaw capacity across clouds after you commit to self-hosting agents. Infra captures multi-cloud deploy, upgrades, and instance management—the work of keeping OpenClaw online, not writing application features.
How it compares
OpenClaw deployment MCP/CLI across clouds—not an OpenClaw skill pack or a generic PaaS one-click template.
Common Questions / FAQ
Who is Clawops for?
Solo builders and small teams running self-hosted OpenClaw who need multi-cloud deploy and instance management orchestrated through MCP-aware agents.
When should I use Clawops?
Use it in Operate when standing up new OpenClaw environments, migrating clouds, or performing ongoing instance management after you have committed to self-hosted agents.
How do I add Clawops to my agent?
Install @Clawops/cli from npm (v1.4.0), configure cloud and OpenClaw credentials per the Clawops repo docs, register an MCP server that runs Clawops with positional arguments mcp and serve (stdio), then test from Claude Code or Cursor.