Skip to main content

Connect Perk to Warp

Give Warp governed access to Perk’s 44 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Perk to Warp in four steps

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

  1. 1

    Add Perk to Runlayer

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

    Adding a connector manually
  2. 2

    Connect Warp to Runlayer

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

    Warp setup guide
  3. 3

    Sign in to Perk

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

  4. 4

    Use Perk from Warp

    Perk’s approved tools appear in Warp. Every call is checked against policy and recorded.

Tools

44 Perk tools in Warp

Runlayer policy decides which of these Warp users can call.

  • Approvals get trip approval links

    Get a link the user can open to approve or decline a specific trip.

  • Cars build car deeplink

    Generate a Perk deep-link to the Configure page for a chosen car offer, with that offer preselected, so the user can complete the booking.

  • Cars get car search results

    Fetch available car rental offers for a search.

  • Cars list car delivery addresses

    List the account's car delivery and collection addresses - locations where a rental car can be delivered to and picked up from, instead of a rental office.

  • Cars search car places

    Search for airports, cities, and addresses by name, to resolve the place objects required by start_car_search's pick_up_location/drop_off_location parameters.

  • Cars start car search

    Start a car rental search.

  • Events create event

    Create a new Perk Event.

  • Events list event attendance

    List attendees for a specific Perk Event.

See all 44 Perk tools

Control

What Runlayer can see and stop in Warp

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

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

Frequently asked questions

Connect more

Find another combination