MCP Tools DirectoryAbout this integration
MCP server bridging Claude Code to the OpenClaw gateway management plane via JSON-RPC.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.6.0
- Package
- openclaw-control-mcp
- Last compatibility test
- Not independently tested
Connect your agent
openclaw-control-mcpThe publisher warns that the gateway wire format is reverse-engineered and that many tools are destructive or secret-bearing. Pairing, permissions, exposure, and human confirmation controls require operator review. This was documentation review only, not a live gateway or security test.
Capabilities: Inspect OpenClaw gateway status, sessions, agents, and logs, Manage scheduled jobs, configuration, skills, and approvals, Connect to multiple configured OpenClaw gateway instances
Connected profiles
Additional details
io.github.smurfy92/openclaw-control-mcp
Source ↗ · Checked 2026-09-170.6.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17openclaw-control-mcp
Source ↗ · Checked 2026-09-190.8.1
Source ↗ · Checked 2026-09-19The default MCP transport is stdio and the client launches the executable; optional Streamable HTTP mode is separately enabled and has additional bearer and bind-address requirements.
Source ↗ · Checked 2026-09-19The gateway flow combines a generated Ed25519 device identity, one-time Control-panel approval, a cached per-gateway device token, and optional gateway token or password, which is outside the single native authentication taxonomy.
Source ↗ · Checked 2026-09-19The stdio wrapper requires the WebSocket URL used by the OpenClaw Control panel and can read the URL and gateway credentials from its protected store or documented environment variables.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19