OpenClaw - OpenSRE Documentation

Overview

OpenSRE integrates with OpenClaw in a native, one-way support loop:

OpenSRE can search recent OpenClaw conversations during an investigation.
OpenSRE can read full OpenClaw threads for extra engineering context.
OpenSRE writes completed RCA findings back into OpenClaw through the OpenClaw bridge.

OpenSRE no longer ships a separate opensre-mcp command. You do not need to register OpenSRE itself as an MCP server inside OpenClaw.

Prerequisites

Node.js v22.12+ in the same shell that runs OpenSRE
OpenClaw CLI installed and healthy (openclaw --help)
OpenClaw Gateway running for conversation tools / write-back

Preflight:

node -v
openclaw --help
openclaw gateway status

If you use nvm:

nvm install 22
nvm use 22
node -v
openclaw --help

nvm alias default 22 only affects future shells — it does not switch the current shell that launches uv run opensre.

Setup

Option 1: Interactive CLI / onboard

make install
uv run opensre onboard
# or
uv run opensre integrations setup openclaw

Recommended bridge settings (stdio — what setup configures):

OPENCLAW_MCP_MODE=stdio
OPENCLAW_MCP_COMMAND=openclaw
OPENCLAW_MCP_ARGS="mcp serve"

Option 2: Environment variables

Variable	Meaning	Default
`OPENCLAW_MCP_MODE`	Bridge transport: `stdio`, `streamable-http`, or `sse`	`streamable-http` (setup forces `stdio`)
`OPENCLAW_MCP_COMMAND`	Executable for `stdio` mode	`openclaw`
`OPENCLAW_MCP_ARGS`	Space-separated args for `stdio` mode	`mcp serve`
`OPENCLAW_MCP_URL`	Remote MCP endpoint for `streamable-http` / `sse`	none
`OPENCLAW_MCP_AUTH_TOKEN`	Optional bearer token for remote MCP transports	empty

Setup locks stdio mode and clears URL/token fields so you do not accidentally point at the Control UI.

Credentials

For local stdio, the OpenClaw CLI on PATH is enough. For remote MCP (streamable-http / sse), set OPENCLAW_MCP_URL and optionally OPENCLAW_MCP_AUTH_TOKEN. Do not use http://127.0.0.1:18789/ as the MCP URL — that is the OpenClaw Control UI / Gateway, not the MCP bridge.

Investigation tools

Tool	What it does
`search_openclaw_conversations`	Find recent related conversation context
`get_openclaw_conversation`	Read a full thread
`send_openclaw_message`	Append a concrete follow-up
`list_openclaw_tools`	List tools exposed by the OpenClaw MCP bridge
`call_openclaw_tool`	Lower-level raw bridge call (fallback)

Preferred investigation path: search → get conversation → send message. Raw bridge tools remain available as fallback.

Write-back behavior

After every completed investigation, OpenSRE attempts to write the full RCA report back into OpenClaw.

If state contains openclaw_context.conversation_id, OpenSRE appends to that conversation first.
Otherwise it creates a new conversation with the RCA report, root cause, remediation steps, and confidence score.

Accurate RCA

OpenClaw improves RCA with engineering context, but is not enough alone. Also configure at least one of:

Grafana or Datadog for metrics/logs/traces
AWS for infra topology and runtime state
GitHub for deploy/code-change context

Smoke test:

uv run opensre investigate -i tests/fixtures/openclaw_test_alert.json

Good local validation sequence:

uv run opensre integrations verify openclaw
uv run opensre integrations verify grafana
uv run opensre integrations verify github
uv run opensre investigate -i tests/fixtures/openclaw_test_alert.json

Contributor regression coverage:

tests/integrations/openclaw/test_integration.py
tests/tools/test_openclaw_mcp_tool.py
tests/utils/test_openclaw_delivery.py
tests/e2e/openclaw/ — see its README

Verify

uv run opensre integrations verify openclaw
uv run opensre health

Verify exercises a live MCP list_tools call (plus stdio preflight). If it fails:

openclaw gateway status
openclaw gateway run
uv run opensre integrations verify openclaw

Troubleshooting

Symptom	Fix
Node.js … is required	Switch the current shell to Node `22.12+` (`nvm use 22` or `brew install node@22`), then re-run `openclaw --help`
Verify fails against `http://127.0.0.1:18789/`	That URL is the Control UI/Gateway, not MCP — use `stdio` with `openclaw mcp serve`
`Connection closed` / `ECONNREFUSED`	Gateway not running — `openclaw gateway status` then `openclaw gateway run`
`Command not found: openclaw`	Install the OpenClaw CLI or set `OPENCLAW_MCP_COMMAND` to the full path

Security

Prefer local stdio over exposing a remote MCP endpoint when possible.
Treat OPENCLAW_MCP_AUTH_TOKEN as a secret — store it in the keyring / .env, not source control.
Write-back posts RCA content into OpenClaw; keep conversation access appropriately scoped.

​Overview

​Prerequisites

​Setup

​Option 1: Interactive CLI / onboard

​Option 2: Environment variables

​Credentials

​Investigation tools

​Write-back behavior

​Accurate RCA

​Verify

​Troubleshooting

​Security