smurfy92

Openclaw Control MCP — Development skill for Claude Code

Development community

The OpenClaw control plane MCP server — 134 typed tools to operate the gateway's full management surface (cron, sessions, agents, channels, skills, secrets, doctor, …) from Claude Code, Cursor, or any.

How to install Openclaw Control MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open smurfy92/openclaw-control-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Openclaw Control MCP does

Alternatives in Development

Zeron — A native control plane for Claude Code, Codex, Cursor, Devin and other coding agents 1.4k ★
OpenSquirrel — For people who get distracted by agents 1.3k ★
Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★

README

openclaw-control-mcp

[![npm](https://img.shields.io/npm/v/openclaw-control-mcp.svg)](https://www.npmjs.com/package/openclaw-control-mcp) [![npm downloads](https://img.shields.io/npm/dm/openclaw-control-mcp.svg)](https://www.npmjs.com/package/openclaw-control-mcp) [![CI](https://github.com/smurfy92/openclaw-control-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/smurfy92/openclaw-control-mcp/actions/workflows/ci.yml) [![license](https://img.shields.io/npm/l/openclaw-control-mcp.svg)](./LICENSE) [![Node](https://img.shields.io/node/v/openclaw-control-mcp.svg)](https://www.npmjs.com/package/openclaw-control-mcp)

**The OpenClaw control plane MCP server.** Operate the gateway's full management surface from Claude Code, Cursor, or any MCP client — list and trigger crons, inspect sessions, configure agents and channels, manage skills and secrets, drive the doctor memory plane, pair devices, approve exec/plugin calls. **143 typed tools** covering every JSON-RPC method the gateway publishes.

![demo](docs/assets/demo.gif)

Different from the upstream [`openclaw-mcp`](https://www.npmjs.com/package/openclaw-mcp), which only wraps `/v1/chat/completions`. This one talks the JSON-RPC protocol used by the OpenClaw Control panel — so you can operate the gateway itself (its crons, sessions, agents, channels, skills, secrets, …), not just chat through it.

Without vs with

**Without `openclaw-control-mcp`** — you bounce between the Control panel UI, your terminal, and Claude Code. "List my crons" means opening the SPA. "Tail this agent session" means staying in the panel and refreshing. "Why did this skill fail?" means hunting through `logs.tail` manually. The assistant can chat through the gateway but it cannot **operate** it.

**With `openclaw-control-mcp`** — the same assistant queries `openclaw_cron_list`, follows up with `openclaw_sessions_tail` to watch a turn in flight, asks `openclaw_skills_status` for diagnostic data, rotates a secret via `openclaw_secre