Skip to main content
Book a demo

Connect Zip to Windsurf

Give Windsurf governed access to Zip’s 65 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Windsurf setup guide

Set up

Add Zip to Windsurf in four steps

Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.

  1. 1

    Add Zip to Runlayer

    Zip isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Windsurf to Runlayer

    Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Zip’s 65 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to Zip

    Sign in the way Zip requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Zip from Windsurf

    Zip’s approved tools appear in Windsurf. Every call is checked against policy and recorded.

Tools

65 Zip tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Get agreement

    Fetch a single agreement (contract) by GUID.

  • Get attachment

    Get a single attachment (document) by GUID.

  • Get attachment download URL

    Get a single-use download URL for the primary (latest) version of an attachment.

  • Get cash back

    Get a single virtual card cash back by GUID.

  • Get category

    Fetch a single taxonomy node (category) by GUID.

  • Get change order

    Get a single change order (purchase requisition of type CHANGE_ORDER) by GUID.

  • Get context library

    Fetch a single context library entry by GUID, including its latest published version (purpose, instructions, version number).

  • Get credit memo

    Get a single credit memo by GUID.

See all 65 Zip tools

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 Zip 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

Find another combination