Skip to main content
OpenClaw is a local-first personal agent and gateway that connects messaging channels, browser, files, and shell to LLMs. It extends through skills (distributed via ClawHub) and MCP servers, and acts as both an MCP client and an MCP server. Both surfaces accept Smithers.

​
Register the MCP server

The fastest path is mcp add, which writes its server straight into OpenClaw’s ~/.openclaw/openclaw.json: 
bunx smithers-orchestrator mcp add --agent openclaw
To do it by hand, OpenClaw stores MCP servers in ~/.openclaw/openclaw.json under mcp.servers. Add Smithers as a stdio server: 
{
  "mcp": {
    "servers": {
      "smithers": {
        "command": "bunx",
        "args": ["smithers-orchestrator", "--mcp"]
      }
    }
  }
}
Or manage it from the CLI: 
openclaw mcp set smithers '{"command":"bunx","args":["smithers-orchestrator","--mcp"]}'
openclaw mcp list
The semantic tools (list_workflows, run_workflow, watch_run, resolve_approval, and the rest) become available to OpenClaw’s agent. Full reference: MCP Server.

​
Install the skill

OpenClaw discovers skills from ~/.agents/skills/ (among other locations), which is exactly where the cross-agent command installs them: 
bunx smithers-orchestrator skills add
Or place the onboarding skill there by hand: 
mkdir -p ~/.agents/skills/smithers
curl -fsSL https://raw.githubusercontent.com/smithersai/smithers/main/skills/smithers/SKILL.md \
  -o ~/.agents/skills/smithers/SKILL.md
curl -fsSL https://smithers.sh/llms-full.txt \
  -o ~/.agents/skills/smithers/llms-full.txt
OpenClaw’s own skill registry is ClawHub (openclaw skills install <slug>); the Smithers skill installs directly into the skills directory rather than through the hub.

​
See also