Skip to Content
runelay
Connect agents

Grokbot

Grok CLI with one block in ~/.grok/config.toml, or a hosted Grok Bot by remote MCP connector.

Grok runs in two places, and each one connects in a different way:

  • Grok CLI on your computer reads ~/.grok/config.toml. Follow Grok CLI.
  • A hosted Grok Bot has no local filesystem, so it never reads that file. Follow Hosted Grok Bot.

Grok CLI on your computer

Add runelay 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.

~/.grok/config.toml
[mcp_servers.runelay]
url = "https://runelay.example.com/v1/mcp"
headers = { Authorization = "Bearer rnl_..." }

Open a new Grok session. A .grok/config.toml inside a repo can override the global entry.

runelay connect does this for you. It also turns Grok's native memory off, so Grok saves memory only in runelay:

~/.grok/config.toml
[memory]
enabled = false

[memory_v2]
enabled = false

Then run runelay doctor to check that memory is off, the MCP is registered and no instruction tells Grok to save memory somewhere else. The native memory table covers the other agents.

Hosted Grok Bot

A hosted bot runs on someone else's server. It cannot reach 127.0.0.1 on your computer, and it cannot read files there.

  1. Put runelay on a public HTTPS URL. A VPS or your own domain, behind HTTPS. See Self-hosting.

  2. Create a key for the bot. In the panel, create an agent key (rnl_…) named after the bot. You can revoke it without touching your other agents.

  3. Reconnect your accounts in runelay. The bot's logins do not leave the bot. Connect GitHub, Linear and the rest again in the runelay panel.

  4. Add runelay as a remote MCP connector in the bot's settings:

    URL      https://runelay.example.com/v1/mcp
    Header   Authorization: Bearer rnl_...

    Put the header in the bot's protected or secret field, not in the prompt.

  5. Move memories and skills. Ask the bot to export its memories, remove secrets, and send them with import_memory in batches of up to 200. Skills go with write_skill and write_skill_file. The copyable prompt is on runelay.com/guides/grokbot.

  6. Turn off the bot's own memory, so it saves only through runelay.

  7. Run both for a while. Keep the old connectors until the bot works through runelay, then disconnect them.

Step by step, with what Grok gets once connected: runelay.com/guides/grokbot.

On this page