Skip to main content
Book a demo

Connect Zip to Goose

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

Book a demo Goose setup guide

Set up

Add Zip to Goose in four steps

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

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Zip’s 65 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

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

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

Tools

65 Zip tools in Goose

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Goose 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 Goose runs it.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination