clawops MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  await execPrivileged(session, `docker exec openclaw rm -rf ${stagingInContainer}`, signal)

      'http://metadata.google.internal/computeMetadata/v1/instance/id',

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    execSync(`${cmd} "${url}"`, { stdio: 'ignore' })

      `cat /home/clawops/.ssh/authorized_keys 2>/dev/null || true`,

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

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

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

[mcp_servers.clawops]
command = "npx"
args = ["-y", "@clawops/cli"]

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

{
  "servers": {
    "clawops": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@clawops/cli"
      ]
    }
  }
}