runelay

runelay+Hermes AgentGuide

Connect Hermes Agent to Runelay

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

What Hermes Agent gets

Without a gateway, Hermes Agent 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. Add it to ~/.hermes/config.yaml

    These bots usually run on a server so they can answer in chat around the clock, and a server cannot reach 127.0.0.1 on your laptop. Run Runelay on the same server, or anywhere the bot can reach over HTTPS. Hermes reads remote MCP servers from mcp_servers, with the key in headers. Replace the URL and the key with yours. With the desktop app the URL is http://127.0.0.1:4312/v1/mcp.

    mcp_servers:
      runelay:
        url: "https://runelay.example.com/v1/mcp"
        headers:
          Authorization: "Bearer rnl_..."
  4. No CLI shortcut yet

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

  5. Reload the servers

    Run /reload-mcp in a Hermes session, or restart Hermes. A running messaging gateway (hermes gateway run) picks up the change on its own within about a minute. The Runelay tools show up as mcp_runelay_*.

Bring what you already have

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

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

Once connected, in Hermes Agent

  • 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 Hermes Agent?

No. Hermes Agent 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.

Can I hide some Runelay tools from Hermes?

Yes. Add a tools block to the runelay entry with include or exclude, the same way you filter any MCP server in Hermes.

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