Skip to main content
Book a demo

Connect Skyvern to Claude

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

Book a demo Claude setup guide

Set up

Add Skyvern to Claude in four steps

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

  1. 1

    Approve Skyvern in Runlayer

    Add Skyvern from the catalog and choose who can use it and which of its tools are allowed.

  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, Skyvern’s 77 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Skyvern

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

  4. 4

    Use Skyvern from Claude

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

Tools

77 Skyvern tools in Claude

Runlayer policy decides which of these Claude users can call. 34 read data only and 11 can change or delete data.

  • Create browser session

    Create a new browser session to start interacting with websites.

  • Close browser session

    Close a browser session when you're done.

  • List browser sessions

    List all active browser sessions.

  • Get browser session

    Get details about a specific browser session -- status, timeout, availability.

  • Connect to browser session

    Connect to an existing browser -- a cloud session by ID or any browser via CDP URL.

  • Perform browser action (ai)

    Perform actions on a page by describing what to do in plain English.

  • Extract data from page (ai)

    Extract structured data from the current page using AI with screenshots and a dedicated extraction LLM.

  • Validate page condition (ai)

    Check if a condition is true on the current page — cheapest AI option for yes/no questions.

See all 77 Skyvern 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 Skyvern 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