Skip to Content
runelay
Connect agents

OpenClaw

One openclaw mcp set command.

Add runelay to OpenClaw with your endpoint and an agent key (rnl_…). Replace the URL and the key with yours; with the desktop app the URL is http://127.0.0.1:4312/v1/mcp.

These bots usually run on a server so they can answer in chat around the clock. A server cannot reach 127.0.0.1 on your laptop, so run runelay on the same server or anywhere the bot reaches over HTTPS.

openclaw mcp set runelay '{"url":"https://runelay.example.com/v1/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${RUNELAY_KEY}"}}'

Set RUNELAY_KEY to your rnl_ key in the Gateway's environment, then run openclaw gateway restart and openclaw mcp probe runelay to list the tools. Set transport explicitly: without it OpenClaw falls back to SSE.

When OpenClaw runs on the same computer, runelay connect writes mcp.servers.runelay into ~/.openclaw/openclaw.json with the same url, "transport": "streamable-http" and the key itself in headers (not ${RUNELAY_KEY}). It only edits a file that parses as plain JSON: with JSON5 comments or trailing commas it leaves the file alone and asks you to use the command above. It also turns OpenClaw's memory plugin off with "plugins": { "slots": { "memory": "none" } } in ~/.openclaw/openclaw.json, so OpenClaw saves memory only in runelay. See the native memory table for the other agents.

Step by step, with what OpenClaw gets once connected: runelay.com/guides/openclaw.