Skip to main content
Book a demo

Connect Zip to Cursor

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

Book a demo Cursor setup guide

Set up

Add Zip to Cursor in four steps

Admins approve the server once. Everyone in Cursor 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 Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Zip’s 65 tools show up in Cursor’s own tool list.

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

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

Tools

65 Zip tools in Cursor

Runlayer policy decides which of these Cursor 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 Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Zip call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination