Clawops MCP Server

MCP-native infrastructure ops for OpenClaw, with read-only mode, destructive-action confirmation, and audit logs built in. Its 20 documented tools cover clawops, workflow. It runs locally over stdio via the published package.

People who work with clawops and workflow and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-09-26 · ★ 6 · #25 OF 165 MAINTAINED CLOUD INFRASTRUCTURE · VERIFIED 2026-09-30

MPL-2.0 · TypeScript servers · how we verify → /methodology

01 · Install Clawops

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Code

claude mcp add dfridkin-clawops -- npx -y @clawops/cli

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "dfridkin-clawops": {
      "command": "npx",
      "args": [
        "-y",
        "@clawops/cli"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MPL-2.0 - declared in the repository

npm package @clawops/cli - the @clawops scope differs from the repo owner (dfridkin); confirm it's the project's official package

registry namespace io.github.dfridkin is GitHub-verified and matches the repo owner

03 · What Clawops can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can run diagnostics: local prerequisites, and with a stack, remote health, list all stacks and their state, read a remote config value, and list running agents.

The 20 tools it gives your agent

Extracted from the project's README - what clawops lets an agent do.

clawops_status
- Show stack outputs (what is deployed, not whether it works)
clawops_doctor
- Run diagnostics: local prerequisites, and with a stack, remote health
clawops_logs_tail
- Tail OpenClaw logs
clawops_monitor
- Sample gateway and host metrics
clawops_stacks_list
- List all stacks and their state
clawops_config_get
- Read a remote config value
clawops_agents_list
- List running agents
clawops_up
- Provision or update a stack
clawops_destroy
- Destroy a stack (elicits confirmation)
clawops_apply
- Apply a plan file
clawops_plan
- Generate a deploy plan
clawops_config_set
- Write a remote config value
show all 20 tools
clawops_config_unset
- Remove a remote config key
clawops_config_validate
- Validate the deployed config against the OpenClaw schema
clawops_gateway_restart
- Restart the gateway (elicits confirmation)
clawops_harden
- Apply hardening modules; join or leave a tailnet (elicits confirmation)
clawops_init
- Register a stack and write ~/.clawops/config.json (no cloud resources)
clawops_workflow_deploy_app
- End-to-end deploy: plan → confirm → apply → status
clawops_workflow_recover
- Diagnostic workflow for an unhealthy stack
clawops_task_status
- Poll a long-running task

Latest releases

v2.1.3 · 2026-09-23

clawops_init registers a stack over MCP, so a client can bootstrap from nothing. Every · clawops tool needs a config, and creating one was a terminal-only act - so on a machine that had · never run clawops, every tool…

v2.1.2 · 2026-09-23

Every MCP tool now sends its description. The descriptions in spec/mcp-tools.yaml - each · written to say when to use a tool and when to reach for a different one - were generated into · nothing and passed to…

v2.1.1 · 2026-09-23

clawops with no command, started over a pipe, serves MCP instead of printing help. The · things that start MCP servers routinely start them by running the package's binary with no · arguments. Glama's directory build…

04 · Who maintains Clawops

clawops is maintained by dfridkin. It's the only MCP server we track from this author; the repo dates to May 2026.

05 · Facts

category
cloud infrastructure - ranked #25 of 165 actively-maintained cloud infrastructure servers as of 2026-09-30.
release cadence
10+ releases in the last 90 days (latest 2026-09-23)
registry
io.github.dfridkin/clawops (active, first published 2026-05-13 · 16 versions)
packages
npm:@clawops/cli

06 · Clawops FAQ

Is Clawops still maintained?

Yes - as of 2026-09-30, its last commit was 2026-09-26 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

What can Clawops do?

With this server connected, an agent can run diagnostics: local prerequisites, and with a stack, remote health, list all stacks and their state, read a remote config value, and list running agents.

How do I install Clawops?

Run `npx -y @clawops/cli`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.

Does Clawops run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Clawops

More cloud infrastructure MCP servers · Cortex RMCP · Arcane RMCP (dinglebear-ai) · Synapse RMCP (dinglebear-ai) · Uxspot MCP · Boxpdf

More TypeScript MCP servers · DERO MCP Server · Oorep MCP · Dgmo MCP · RPG Maker MV Ultimate MCP · OpenWork MCP Gateway · see all