runelay

runelay+GrokbotGuide

Connect Grokbot to Runelay

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

What Grokbot gets

Without a gateway, Grokbot 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 ~/.grok/config.toml

    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. Or let the CLI do it

    runelay login saves a key for this computer and runelay connect registers Runelay in Claude Code, Codex, Cursor and Grok at once.

    $curl -fsSL runelay.com/cli | sh
    $runelay login && runelay connect
  5. Give Grok the runelay instructions

    Add this to ~/.grok/AGENTS.md, which Grok reads at the start of every session, so it goes through runelay first: context, tools and memory. Then open a new session.

    runelay instructions for GrokContext first, tools by search, memory that every agent reads.

Bring what you already have

runelay migrate reads the remote [mcp_servers.*] in ~/.grok/config.toml, with their headers. Grok keeps its MCP logins in ~/.grok/mcp_credentials.json, so OAuth accounts arrive connected on every platform, with no Keychain prompt. Servers with a command stay in Grok.

runelay push sends ~/.grok/skills and ~/.grok/AGENTS.md, which arrives as a pinned memory. runelay pull writes the shared brief into ~/.grok/AGENTS.md, only between the Runelay markers.

Once connected, in Grokbot

  • 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 Grokbot?

No. Grokbot 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 a project use its own config?

Yes. Grok also reads [mcp_servers] from .grok/config.toml inside a repo, and a project server with the same name replaces the global one entirely.

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