clawops MCP server

clawops

MCP-native infrastructure ops for OpenClaw, with read-only mode, destructive-action confirmation, and audit logs built in.

clawops is a CLI and MCP server for deploying and operating self-hosted OpenClaw instances. Provision on AWS, GCP, Azure, or any Linux VM, then manage day-to-day operations from the terminal, or let Claude Code and Cursor drive them through typed MCP tools with explicit safety controls.

What's new in 2.0.1

A patch release, and a large one: in 2.0.0 no cloud deploy succeeded by any path. Every item below is a fix or an addition in 2.0.1. The reasoning behind each one is in its commit message, and the decisions that came out of them are in docs/decisions/.

Deploying to a cloud

one already on $PATH (ADR 0010).

• clawops plan → clawops apply provisions a cloud stack and deploys OpenClaw onto it.
• clawops up deploys to AWS, GCP and Azure, running the same path as plan → apply.
• clawops installs the Pulumi CLI it needs into ~/.clawops/.pulumi-cli, or uses a compatible

(ADR 0011).

• clawops creates and stores the passphrase its state backend requires

passes them to the cloud firewall. auto resolves this machine's address.

• clawops plan takes --ssh-cidr, --gateway-cidr and --publish-gateway, and apply

itself, and the plan records the concrete type.

• clawops plan stops, and names the cause, when it cannot open the state backend.
• --instance-type takes a clawops alias (micro–gpu) or a machine type your cloud names

azure-native:subscriptionId on Azure.

• Deploys pin the account they were planned against: gcp:project on GCP,

Checking the account before you spend

without a stack. --instance-type points the size check at the size you are deploying.

• clawops doctor --provider checks one cloud's credentials and account setup, with or

type is offered in the region.

• AWS. The account the credentials resolve to, the state bucket, and whether the instance

Pulumi authenticates with.

• GCP. The project, the APIs a deploy needs, and the state bucket.
• Azure. The subscription, the resource providers, the VM size, and the azblob credentials

creating a state bucket with versioning on and public access blocked, naming the change before making it.

• clawops setup runs the same checks and offers to fix what it safely can, enabling an API,

pass or a failure.

• A check clawops could not perform reports as a warning naming the error, rather than as a

• Azure accepts your az login; a service principal is no longer required.

Naming, config and setup

for a name or writing a placeholder (ADR 0012).

• clawops names the state backend after the account it is deploying into, instead of asking you

release, clawops doctor will tell you whether yours is usable.

• A name you type instead is checked against the rules of the cloud that has to accept it.
• clawops init keeps the stacks already in your config.
• clawops init generates an SSH key that clawops can read. If you ran init before this

your chosen provider needs.

• gcloud config set project is honoured.
• The setup wizard writes model configuration that OpenClaw accepts, and installs the plugin

deployment region and recorded in the plan. Needs bedrock:ListInferenceProfiles.

• Amazon Bedrock works: the right transport, and an inference profile resolved against your

While a deploy is running

Shortened. The full README is on GitHub.