Skip to main content
Book a demo

Connect Perk to VS Code

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

Book a demo VS Code setup guide

Set up

Add Perk to VS Code in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Perk’s 44 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code 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 VS Code

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

Tools

44 Perk tools in VS Code

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Block output after it runs (available)

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

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination