Skip to main content

Connect Zip to Raycast

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

Set up

Add Zip to Raycast in four steps

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

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

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

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

Tools

65 Zip tools in Raycast

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Raycast as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Raycast yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination