Skip to main content
Book a demo

Connect Perk to Claude

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

Book a demo Claude setup guide

Set up

Add Perk to Claude in four steps

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

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Perk’s 44 tools show up in Claude’s own tool list.

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

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

Tools

44 Perk tools in Claude

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination