runelay+OpenClawGuide
Connect OpenClaw to Runelay
Runelay, an open source MCP gateway, gives OpenClaw one endpoint for every account you connected. Add it once and OpenClaw sees the same tools, skills and memories as your other agents.
What OpenClaw gets
Without a gateway, OpenClaw connects to every MCP server on its own, loads each full tool list at connect and keeps its own logins.
With Runelay it connects to one endpoint, /v1/mcp. The gateway holds the credentials and exposes a small set of tools to search and call everything behind it. In our benchmark that was 1,045 context tokens at connect for 125 tools (Runelay 0.3.2, 14 Nov 2026, full numbers).
Set it up
Run Runelay
Use the desktop app, or install the server with Docker. Both serve the panel and the MCP endpoint on port 4312.
$curl -fsSL runelay.com/install | shCreate a key
In the panel, the agent setup guide creates a key that starts with
rnl_. Each agent can have its own key, so you can revoke one without touching the others.Save it with
openclaw mcp setThese bots usually run on a server so they can answer in chat around the clock, and a server cannot reach
127.0.0.1on your laptop. Run Runelay on the same server, or anywhere the bot can reach over HTTPS. The command writes a Streamable HTTP server undermcp.serversin the OpenClaw config. SetRUNELAY_KEYto yourrnl_key in the Gateway's environment, so the key stays out of the config file. Replace the URL and the key with yours. With the desktop app the URL ishttp://127.0.0.1:4312/v1/mcp.openclaw mcp set runelay '{"url":"https://runelay.example.com/v1/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${RUNELAY_KEY}"}}'No CLI shortcut yet
runelay connectwrites Claude Code, Codex, Cursor and Grok, not OpenClaw. Add Runelay by hand once; the key stays valid until you revoke it in the panel.Restart the Gateway and check
Run
openclaw gateway restartso the agents pick up the new server, thenopenclaw mcp probe runelayto open a live connection and list the Runelay tools.$openclaw gateway restart && openclaw mcp probe runelay
Bring what you already have
runelay migrate does not read OpenClaw yet, so its MCP servers and logins stay where they are. Add the remote servers you use in the Runelay panel by URL and OpenClaw reaches them through the endpoint.
runelay push and runelay pull do not touch OpenClaw files either. Memories and skills reach it through the endpoint, with search_context, read_memory and read_skill.
Once connected, in OpenClaw
search_toolsandcall_toolreach every connected account, such as Linear, GitHub and Notion.executechains several calls in a sandboxed JavaScript runtime.search_context,read_memoryandwrite_memoryshare memory with your other agents.read_skillserves the same skills to every agent.
Questions
Do my account tokens reach OpenClaw?
No. OpenClaw only holds the Runelay key. OAuth tokens and API keys stay on your server, encrypted with AES-256-GCM using your RUNELAY_SECRET.
Do I need Docker?
No. The desktop app for Mac, Windows and Linux runs the same server on your computer. Docker is for a server that stays on.
Can I keep the MCP servers I already configured?
Yes. Runelay is one more MCP server in the config. If you migrate them, running runelay migrate --replace removes the migrated ones and leaves only Runelay.
Why streamable-http?
OpenClaw falls back to SSE when transport is missing. The Runelay endpoint speaks Streamable HTTP, so set it explicitly.