runelay+Kimi CodeGuide
Connect Kimi Code to Runelay
Runelay, an open source MCP gateway, gives Kimi Code one endpoint for every account you connected. Add it once and Kimi Code sees the same tools, skills and memories as your other agents.
What Kimi Code gets
Without a gateway, Kimi Code 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 to
~/.kimi-code/mcp.jsonKimi Code CLI reads user-level MCP servers from
~/.kimi-code/mcp.json, or$KIMI_CODE_HOME/mcp.json. An entry with aurland notransportis an HTTP server, andheadersis sent on every request. You can also add it from the TUI with/mcp-config. Replace the URL and the key with yours. With the desktop app the URL ishttp://127.0.0.1:4312/v1/mcp.{ "mcpServers": { "runelay": { "url": "https://runelay.example.com/v1/mcp", "headers": { "Authorization": "Bearer rnl_..." } } } }No CLI shortcut yet
runelay connectwrites Claude Code, Codex, Cursor and Grok, not Kimi Code. Add Runelay by hand once; the key stays valid until you revoke it in the panel.Open a new session and check
A server added in
mcp.jsonjoins only sessions created after the change. Open a new session and run/mcpto see Runelay connected.
Bring what you already have
runelay migrate does not read Kimi Code yet, so its MCP servers and logins stay where they are. Add the remote servers you use in the Runelay panel by URL and Kimi Code reaches them through the endpoint.
runelay push and runelay pull do not touch Kimi Code files either. Memories and skills reach it through the endpoint, with search_context, read_memory and read_skill.
Once connected, in Kimi Code
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 Kimi Code?
No. Kimi Code 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 keep the key out of mcp.json?
Yes. Kimi Code accepts bearerTokenEnvVar in place of the Authorization header: name an environment variable that holds your rnl_ key.