runelay+AntigravityGuide
Connect Antigravity to Runelay
Runelay, an open source MCP gateway, gives Antigravity one endpoint for every account you connected. Add it once and Antigravity sees the same tools, skills and memories as your other agents.
What Antigravity gets
Without a gateway, Antigravity 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
mcp_config.jsonThe global file is
~/.gemini/config/mcp_config.json, and.agents/mcp_config.jsonin a workspace covers one project. To open it, use View raw config under Manage MCP Servers in the IDE, or Copy Config File Path under Customizations in the app. Replace the URL and the key with yours. With the desktop app the URL ishttp://127.0.0.1:4312/v1/mcp.{ "mcpServers": { "runelay": { "serverUrl": "https://runelay.example.com/v1/mcp", "headers": { "Authorization": "Bearer rnl_..." } } } }No CLI shortcut yet
runelay connectwrites Claude Code, Codex, Cursor and Grok, not Antigravity. Add the block above by hand once; the key stays valid until you revoke it in the panel.Restart Antigravity
Save the file and reopen Antigravity. Runelay shows up in the MCP Servers list with its tools.
Bring what you already have
runelay migrate does not read Antigravity yet, so its MCP servers and logins stay where they are. Add the remote servers you use in the Runelay panel by URL and Antigravity reaches them through the endpoint. The Gemini file migrate reads, ~/.gemini/settings.json, belongs to the Gemini CLI, not to Antigravity.
runelay push and runelay pull do not touch Antigravity files either. Memories and skills reach it through the endpoint, with search_context, read_memory and read_skill.
Once connected, in Antigravity
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 Antigravity?
No. Antigravity 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 entry in mcp_config.json and nothing else in the file changes. runelay migrate does not read Antigravity, so add those servers in the Runelay panel if you want every agent to share them.
Why serverUrl?
Antigravity reads remote servers from serverUrl and also accepts url; httpUrl is not supported. Remote servers must speak Streamable HTTP, which is what the Runelay endpoint serves.