Skip to main content
Book a demo

Connect Zip to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Zip to GitHub Copilot in four steps

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

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Zip’s 65 tools through the plugin’s search and execute tools.

    GitHub Copilot 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 GitHub Copilot

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

Tools

65 Zip tools in GitHub Copilot

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

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

Frequently asked questions

Connect more

Find another combination