Install · OpenClaw

Add ChiefLab to OpenClaw

OpenClaw speaks MCP natively. ChiefLab plugs in as a hosted MCP — one config block, no install. Same closed-loop launch flow Cursor / Claude Desktop / Codex agents get.

Try first: run ChiefMO in your browser. Same output your OpenClaw agent will see.

Step 1 — Get an API key

One click at chieflab.io/get-key. Save the clp_dev_ key.

Step 2 — Add to OpenClaw's MCP config

OpenClaw config locations vary by version (typically ~/.openclaw/mcp.json or via the MCP panel in the UI):

{
  "mcpServers": {
    "chieflab": {
      "url": "https://chieflab.io/api/mcp",
      "headers": {
        "Authorization": "Bearer clp_dev_<paste-your-key>"
      }
    }
  }
}

If your OpenClaw build only supports stdio MCP servers (not hosted URLs), use the @chieflab/mcp-server npm bridge:

npm install -g @chieflab/mcp-server
{
  "mcpServers": {
    "chieflab": {
      "command": "chieflab-mcp",
      "env": { "CHIEFLAB_API_KEY": "clp_dev_<paste-your-key>" }
    }
  }
}

Step 3 — Try the closed loop

> I just shipped my product at https://yoursite.com.
  Use ChiefMO to launch it.

OpenClaw picks chiefmo_launch_product, returns a launch pack + signed reviewUrl. Approve in browser. OpenClaw fires chiefmo_publish_approved_post + chiefmo_send_approved_email for each approved action. 24h later, chiefmo_measure_launch_results returns metrics + next-iteration brief.

Same as everywhere else

The full agent instructions, multi-tenant pattern, troubleshooting, and tool catalog are universal across runtimes: