Skip to main content
Book a demo

Connect Skyvern to Cursor

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

Book a demo Cursor setup guide

Set up

Add Skyvern to Cursor in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Skyvern’s 77 tools show up in Cursor’s own tool list.

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

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

Tools

77 Skyvern tools in Cursor

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination