runelay

runelay+MausBotGuide

Connect MausBot to Runelay

Runelay, an open source MCP gateway, gives MausBot one endpoint for every account you connected. Add it once and MausBot sees the same tools, skills and memories as your other agents.

What MausBot gets

Without a gateway, MausBot 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

  1. 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 | sh
  2. Create 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.

  3. Paste it in Plugins → MCP servers → Add server

    MausBot reads a claude mcp add command and fills the address and the Authorization header for you. Under Edit details it is a Connect to a URL server over Streamable HTTP. Replace the URL and the key with yours. With the desktop app the URL is http://127.0.0.1:4312/v1/mcp.

    claude mcp add --scope user --transport http runelay https://runelay.example.com/v1/mcp \
      --header "Authorization: Bearer rnl_..."
  4. No CLI shortcut yet

    runelay connect writes Claude Code, Codex, Cursor and Grok, not MausBot. Add Runelay by hand once; the key stays valid until you revoke it in the panel.

  5. Pick which bots get it

    MausBot tests the server when you add it and turns it on when the tools load. Bots that use every enabled server get Runelay on their next task, with no restart. Bots with their own selection need runelay added under Bot access.

Bring what you already have

runelay migrate does not read MausBot yet, so its MCP servers and logins stay where they are. Add the remote servers you use in the Runelay panel by URL and MausBot reaches them through the endpoint.

runelay push and runelay pull do not touch MausBot files either. Memories and skills reach it through the endpoint, with search_context, read_memory and read_skill.

Once connected, in MausBot

  • search_tools and call_tool reach every connected account, such as Linear, GitHub and Notion.
  • execute chains several calls in a sandboxed JavaScript runtime.
  • search_context, read_memory and write_memory share memory with your other agents.
  • read_skill serves the same skills to every agent.

Questions

Do my account tokens reach MausBot?

No. MausBot 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.

Do all my MausBot bots share the same Runelay?

Yes, when they use the same server entry. Each bot then sees the same connections, skills and memories as Claude Code or Codex outside MausBot.

Try it on your machineFree and open source. Runs on your computer or your server.
Download runelayInstall on your server