Skip to main content
HealOps integrates with OpenClaw in a native, one-way support loop:
  • HealOps can search recent OpenClaw conversations during an investigation.
  • HealOps can read full OpenClaw threads for extra engineering context.
  • HealOps writes completed RCA findings back into OpenClaw through the OpenClaw bridge.
HealOps no longer ships a separate healops-mcp command. You do not need to register HealOps itself as an MCP server inside OpenClaw.

​
Setup

​
0. Preflight the local OpenClaw CLI

Before you onboard OpenClaw in HealOps, make sure the OpenClaw CLI itself is healthy in the same shell:
Expected result:
  • node -v shows Node v22.12+ or newer
  • openclaw --help exits cleanly
  • openclaw gateway status does not fail immediately
If you use nvm, the safe sequence is:
nvm alias default 22 only affects future shells. It does not switch the current shell that launches uv run healops.

​
1. Install and configure HealOps locally

​
2. Configure the HealOps → OpenClaw bridge

Use the guided wizard:
Or use the direct integration setup command:
Recommended bridge settings:

​
3. Verify the bridge

From the repo root:

​
4. Run a smoke test

Use the bundled OpenClaw fixture directly:
If verification still fails, the next manual checks are:

​
Write-back behavior

After every completed investigation, HealOps attempts to write the full RCA report back into OpenClaw.
  • If the investigation state contains an openclaw_context.conversation_id, HealOps first tries to append the result to that conversation.
  • Otherwise, HealOps creates a new OpenClaw conversation containing the RCA report, root cause, remediation steps, and confidence score.

​
Investigation behavior

When OpenClaw is configured, HealOps now prefers the high-signal conversation actions first:
  • search_openclaw_conversations to find recent related context
  • get_openclaw_conversation to read the full thread
  • send_openclaw_message to append a concrete follow-up
The lower-level raw bridge tools remain available, but they are treated as fallback paths instead of the default investigation path.

​
Accurate RCA

OpenClaw improves RCA quality by supplying engineering context, but OpenClaw alone is not enough for a strong investigation. For accurate RCA, also configure at least one of these:
  • Grafana or Datadog for metrics/logs/traces
  • AWS for infra topology and runtime state
  • GitHub for deploy/code-change context
A good local validation sequence is:
Contributor-facing regression coverage for this path lives in:
  • tests/test_openclaw_integration.py
  • tests/tools/test_openclaw_mcp_tool.py
  • tests/utils/test_openclaw_delivery.py
  • tests/e2e/openclaw/ (e2e suite — see the “End-to-end tests” section below)

​
Environment variables

​
Troubleshooting

  • OpenClaw bridge validation failed: Node.js ... is required: switch the current shell to Node 22.12+ or newer. With nvm: nvm install 22 && nvm use 22 && nvm alias default 22. With Homebrew: brew install node@22 && brew link --overwrite node@22. Then re-run openclaw --help before retrying onboarding.
  • uv run healops integrations verify openclaw fails against http://127.0.0.1:18789/: that URL is the OpenClaw Control UI/Gateway, not the MCP bridge. Use stdio mode with openclaw mcp serve.
  • search_openclaw_conversations or write-back fails with Connection closed or ECONNREFUSED: the OpenClaw Gateway is not running. Check openclaw gateway status, then run openclaw gateway run.
  • Command not found: openclaw: install the OpenClaw CLI or point OPENCLAW_MCP_COMMAND at the full executable path.

​
End-to-end tests

The OpenClaw e2e suite lives at tests/e2e/openclaw/. See its README for prerequisites, how to run the suite, scenario layout, and CI behavior.