Connect Neon to Windsurf
Give Windsurf governed access to Neon’s 29 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Neon to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Neon in Runlayer
Add Neon from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Neon’s 29 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Neon
Sign in the way Neon requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Neon from Windsurf
Neon’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
29 Neon tools in Windsurf
Runlayer policy decides which of these Windsurf users can call.
List projects
Lists the first 10 Neon projects in your account.
List organizations
Lists all organizations that the current user has access to.
List shared projects
Lists projects that have been shared with the current user.
Create project
Create a new Neon project.
Delete project
Delete a Neon project
Describe project
Describes a Neon project
Run SQL
Execute a single SQL statement against a Neon database.
Run SQL transaction
Execute a SQL transaction against a Neon database, should be used for multiple SQL statements.
Control
What Runlayer can see and stop in Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Neon call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more