runelay+agentes.chatGuide
Connect agentes.chat to Runelay
Runelay, an open source MCP gateway, gives agentes.chat one endpoint for every account you connected. Add it once and agentes.chat sees the same tools, skills and memories as your other agents.
What agentes.chat gets
Without a gateway, agentes.chat 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.Add it under the MCPs section of Settings
Add a server by URL and paste your
rnl_key in the API key field; agentes.chat sends it as a bearer token. It accepts only a publichttps://address: a private IP or a Tailscale-only name is refused. If Runelay runs only on your tailnet, turn on Tailscale Funnel (tailscale funnel --bg http://127.0.0.1:4312) or give it a domain. Replace the URL and the key with yours. With the desktop app the URL ishttp://127.0.0.1:4312/v1/mcp.Server URL https://runelay.example.com/v1/mcp API key rnl_...No CLI shortcut yet
runelay connectwrites Claude Code, Codex, Cursor and Grok, not agentes.chat. Add Runelay by hand once; the key stays valid until you revoke it in the panel.Check the connector
agentes.chat tests the server when you add it and lists its tools. Runelay shows as Active with 9 tools, and every agent in the workspace can use it; sensitive tools still ask a person for approval. No restart.
Bring what you already have
runelay migrate does not read agentes.chat yet, so its MCP servers and logins stay where they are. Add the remote servers you use in the Runelay panel by URL and agentes.chat reaches them through the endpoint.
runelay push and runelay pull do not touch agentes.chat files either. Memories and skills reach it through the endpoint, with search_context, read_memory and read_skill.
Once connected, in agentes.chat
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 agentes.chat?
No. agentes.chat 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 does it need a public address?
agentes.chat refuses connector addresses on private networks to block SSRF, with no switch for it. A public https address with the rnl_ key in front is enough.