Connect Clay to Windsurf
Give Windsurf governed access to Clay’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Clay to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Clay in Runlayer
Add Clay 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 Clay’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Clay
Sign in the way Clay requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Clay from Windsurf
Clay’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
21 Clay tools in Windsurf
Runlayer policy decides which of these Windsurf users can call. 12 read data only and 3 can change or delete data.
Add company data points
Add data points to companies in an existing search.
Add contact data points
Add data points to contacts in an existing search.
Ask question about accounts
Ask a natural language question about one or more accounts available in Clay Audiences.
Find and enrich company
Find and enrich a single company by domain or LinkedIn URL.
Find and enrich contacts at company
Search for contacts at a company by role, title, name, or department.
Find and enrich list of contacts
Find and enrich specific named contacts at their companies.
Get credits available
Check if credits are available for the workspace.
Get current workspace
Report which Clay workspace this connection is pinned to.
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 Clay 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
