runelay

runelay+CursorGuide

Connect Cursor to Runelay

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

What Cursor gets

Without a gateway, Cursor 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 ~/.cursor/mcp.json

    Replace the URL and the key with yours. With the desktop app the URL is http://127.0.0.1:4312/v1/mcp.

    {
      "mcpServers": {
        "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. Restart the agent

    Cursor loads MCP servers when a session starts. Open a new session and the Runelay tools are there.

Bring what you already have

runelay migrate reads the MCP servers in your Cursor config. Cursor encrypts its OAuth tokens, so those accounts go to a reconnect queue in the panel that walks you through each login once.

runelay push sends the skills in ~/.cursor/skills, so Claude Code and Codex can use them too.

Once connected, in Cursor

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

No. Cursor 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.

Is this the same setup as Claude Code?

Yes. Cursor and Claude Code point at the same endpoint, so both see the same connections, skills and memories.

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