ToolsMCP
clawops
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- dfridkin (GitHub)
- Prerequisites
- Install @clawops/cli from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 2.5.0 · updated
- Official links
Publisher’s description
Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 2.5.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- dfridkin (GitHub)
- Version observed
- 2.5.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.dfridkin%2Fclawops/versions/2.5.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Inspect and manage cloud resources | Publisher description mentions “aws”, “gcp”, “azure”, “deploy”. | No connection check or task run. Capability is as described by the publisher. | Rule cloud-infrastructure matched: “aws”, “gcp”, “azure”, “deploy”. Rule cloud-infrastructure. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@clawops/cli(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.dfridkin/clawops
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.