runelay+NeonIntegration · OAuth login
Neon on Runelay, an open source MCP gateway
Connect Neon once. Claude Code, Cursor, Codex and Grok all use that connection, and the credential never leaves your server.
What this connection does
Serverless Postgres, branches and SQL. Runelay connects to the Neon remote MCP server at https://mcp.neon.tech/mcp and puts its tools behind your own endpoint.
Agents find them with search_tools and run them with call_tool, so the Neon tool list is not loaded into context until it is needed.
Connect Neon
Open the connectors in the panel
Pick Neon from the catalog.
Log in once
A browser tab opens on Neon. Approve the access and close it.
Done
The token is stored encrypted on your server and refreshed by Runelay. Every agent with a Runelay key can use the connection.
Use Neon in your agents
Agents do not need a Neon entry of their own. Point each one at Runelay and Neon is there.
Questions
Does my Neon credential reach the agent?
No. It stays on your Runelay server, encrypted with AES-256-GCM using your RUNELAY_SECRET. Agents only hold their Runelay key.
Do I connect Neon once per agent?
No. You connect it once in Runelay, and every agent that points at your endpoint uses the same connection.
I already have Neon set up in an agent. Can I bring it?
Yes. runelay migrate reads the MCP servers your agents already have. If the CLI can read the token it arrives connected; otherwise it waits in the reconnect queue in the panel.