Connect Carta to Windsurf
Give Windsurf governed access to Carta’s 18 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Carta to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Carta in Runlayer
Add Carta 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 Carta’s 18 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Carta
Sign in the way Carta requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Carta from Windsurf
Carta’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
18 Carta tools in Windsurf
Runlayer policy decides which of these Windsurf users can call.
Call tool
Run a Carta tool that search_tools found.
Cap table chart
Show a visual cap table summary with ownership breakdown by share class.
Discover
List available Carta commands or views across all domains.
Fetch
Execute a named Carta read command.
Get current user
Get the currently authenticated Carta user's profile.
List accounts
List all companies and organizations the current user has access to.
List contexts
Show which firms you have access to in Carta Fund Admin and which one is currently active.
List resources
List all available resources and resource templates.
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 Carta 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