AI-powered browser automation — navigate, click, fill forms, and extract data from any website.
MCP Server: io.github.Skyvern-AI/skyvern
This MCP server provides AI-powered browser automation for workflows that require navigating websites, clicking elements, filling forms, and extracting data. It focuses on browser-based tasks and is described with support for LLM-driven behavior and computer vision, aligned with the repository’s stated approach.
🛠️ Key Features
AI-powered browser automation
Navigate, click, fill forms, and extract data from websites
Uses LLMs and Computer Vision in browser workflows
🚀 Use Cases
Automate browser-based workflows on arbitrary websites
Perform form interactions and data extraction during web navigation
⚡ Developer Benefits
Targets automation through LLMs and vision signals
Supports common automation ecosystems reflected by listed topics (e.g., Playwright, Puppeteer, Selenium)
⚠️ Limitations
Limited to browser-based automation actions explicitly described (navigate, click, fill forms, extract data)
🐉 Automate Browser-based workflows using LLMs and Computer Vision 🐉
Skyvern automates browser-based workflows using LLMs and computer vision. It provides a Playwright-compatible SDK that adds AI functionality on top of playwright, as well as a no-code workflow builder to help both technical and non-technical users automate manual workflows on any website, replacing brittle or unreliable automation solutions.
image
Traditional approaches to browser automations required writing custom scripts for websites, often relying on DOM parsing and XPath-based interactions which would break whenever the website layouts changed.
Instead of only relying on code-defined XPath interactions, Skyvern relies on Vision LLMs to learn and interact with the websites.
How it works
Skyvern was inspired by the Task-Driven autonomous agent design popularized by BabyAGI and AutoGPT -- with one major bonus: we give Skyvern the ability to interact with websites using browser automation libraries like Playwright.
Skyvern uses a swarm of agents to comprehend a website, and plan and execute its actions:
This approach has a few advantages:
Skyvern can operate on websites it's never seen before, as it's able to map visual elements to actions necessary to complete a workflow, without any customized code
Skyvern is resistant to website layout changes, as there are no pre-determined XPaths or other selectors our system is looking for while trying to navigate
Skyvern is able to take a single workflow and apply it to a large number of websites, as it's able to reason through the interactions necessary to complete the workflow
A detailed technical report can be found here.
Skyvern Cloud is a managed cloud version of Skyvern that allows you to run Skyvern without worrying about the infrastructure. It allows you to run multiple Skyvern instances in parallel and comes bundled with anti-bot detection mechanisms, proxy network, and CAPTCHA solvers.
If you'd like to try it out, navigate to app.skyvern.com and create an account.
Run Locally (UI + Server)
Choose your preferred setup method:
Database default: skyvern quickstart and skyvern run server default to a SQLite database at ~/.skyvern/data.db so the pip path works without Postgres or Docker. To use Postgres instead, pass --database-string for an existing database (or omit --no-postgres so quickstart starts its own Postgres container). Docker Compose always uses the bundled Postgres service.
Option A: pip install (Recommended for Python-managed local setup)
The pip quickstart uses SQLite by default. To use a local Postgres container instead, run skyvern quickstart (Postgres container is started unless you pass --no-postgres), or connect to an existing database with --database-string=postgresql+psycopg://user:pass@host:5432/dbname.
Option B: Docker Compose
Use this option if you want everything containerized (Postgres, API, UI) and don't want to install Python/Node locally.
(sqlite3.OperationalError) table organizations already exists — You hit a known bug in pip install skyvern==1.0.31. Fix:
bash
rm ~/.skyvern/data.db # remove the leftover SQLite file
pip install --upgrade skyvern # 1.0.32+ contains the fix
skyvern quickstart
If you are still on 1.0.31 and cannot upgrade, install via uv instead:
bash
uv pip install skyvern
pip install skyvern fails with ResolutionImpossible (litellm / fastmcp) — You hit a dependency-resolution conflict in 1.0.31. Either upgrade to 1.0.32+ or use uv: uv pip install skyvern.
SDK
Skyvern is a Playwright extension that adds AI-powered browser automation. It gives you the full power of Playwright with additional AI capabilities—use natural language prompts to interact with elements, extract data, and automate complex multi-step workflows.
Installation:
Python SDK / cloud API: pip install skyvern
Local server + packaged UI: pip install "skyvern[all]" then run skyvern quickstart
Local server + packaged UI with Postgres: pip install "skyvern[all]" then run skyvern quickstart --database-string=postgresql+psycopg://user:pass@host:5432/dbname
Packaged UI for an existing API: pip install "skyvern[ui]" then set VITE_API_BASE_URL (and VITE_SKYVERN_API_KEY if your API requires a key) and run skyvern run ui
TypeScript: npm install @skyvern/client
AI-Powered Page Commands
Skyvern adds four core AI commands directly on the page object:
Command
Description
page.act(prompt)
Perform actions using natural language (e.g., "Click the login button")
page.extract(prompt, schema)
Extract structured data from the page with optional JSON schema
page.validate(prompt)
Validate page state, returns bool (e.g., "Check if user is logged in")
page.prompt(prompt, schema)
Send arbitrary prompts to the LLM with optional response schema
# 1. Traditional Playwright - CSS/XPath selectorsawait page.click("#submit-button")
# 2. AI-powered - natural languageawait page.click(prompt="Click the green Submit button")
# 3. AI fallback - tries selector first, falls back to AI if it failsawait page.click("#submit-btn", prompt="Click the Submit button")
Core AI Commands - Examples
python
# act - Perform actions using natural languageawait page.act("Click the login button and wait for the dashboard to load")
# extract - Extract structured data with optional JSON schema
result = await page.extract("Get the product name and price")
result = await page.extract(
prompt="Extract order details",
schema={"order_id": "string", "total": "number", "items": "array"}
)
# validate - Check page state (returns bool)
is_logged_in = await page.validate("Check if the user is logged in")
# prompt - Send arbitrary prompts to the LLM
summary = await page.prompt("Summarize what's on this page")
Quick Start Examples
Run via UI:
bash
skyvern run all
Navigate to http://localhost:8080 to run tasks through the web interface. If the packaged UI is missing, skyvern run ui will offer to install the matching UI package.
To run only the packaged UI against an existing Skyvern API, install skyvern[ui] and set the
environment variables below before running skyvern run ui:
VITE_API_BASE_URL (e.g. http://localhost:8000/api/v1) — points the UI at your Skyvern API
VITE_SKYVERN_API_KEY — the API key if your API requires one
VITE_WSS_BASE_URL — WebSocket endpoint (inferred from VITE_API_BASE_URL if unset)
VITE_ARTIFACT_API_BASE_URL — base URL for artifact downloads
from skyvern import Skyvern
# Local mode
skyvern = Skyvern.local()
# Or connect to Skyvern Cloud
skyvern = Skyvern(api_key="your-api-key")
# Launch browser and get page
browser = await skyvern.launch_cloud_browser()
page = await browser.get_working_page()
# Mix Playwright with AI-powered actionsawait page.goto("https://example.com")
await page.click("#login-button") # Traditional Playwrightawait page.agent.login(credential_type="skyvern", credential_id="cred_123") # AI loginawait page.click(prompt="Add first item to cart") # AI-augmented clickawait page.agent.run_task("Complete checkout with: John Snow, 12345") # AI task
TypeScript SDK:
typescript
import { Skyvern } from"@skyvern/client";
const skyvern = newSkyvern({ apiKey: "your-api-key" });
const browser = await skyvern.launchCloudBrowser();
const page = await browser.getWorkingPage();
// Mix Playwright with AI-powered actionsawait page.goto("https://example.com");
await page.click("#login-button"); // Traditional Playwrightawait page.agent.login("skyvern", { credentialId: "cred_123" }); // AI loginawait page.click({ prompt: "Add first item to cart" }); // AI-augmented clickawait page.agent.runTask("Complete checkout with: John Snow, 12345"); // AI taskawait browser.close();
Simple task execution:
python
from skyvern import Skyvern
skyvern = Skyvern()
task = await skyvern.run_task(prompt="Find the top post on hackernews today")
print(task)
Advanced Usage
Control your own browser (Chrome)
Let Skyvern control your existing Chrome browser — with all your cookies, logins, and extensions.
Step 1: Enable remote debugging in Chrome
Open Chrome and navigate to chrome://inspect/#remote-debugging
Click Enable to start the debugging server
You should see: Server running at: 127.0.0.1:9222
TIP
The skyvern init browser command can do this automatically — it opens chrome://inspect/#remote-debugging, waits for you to enable it, and saves the config.
Step 2: Connect Skyvern
Option A — Python Code:
python
from skyvern import Skyvern
skyvern = Skyvern(
base_url="http://localhost:8000",
api_key="YOUR_API_KEY",
browser_address="http://127.0.0.1:9222",
)
task = await skyvern.run_task(
prompt="Find the top post on hackernews today",
)
Restart Skyvern service skyvern run all and run the task through UI or code
Connect Skyvern Cloud to your local browser
Let Skyvern Cloud control a Chrome browser running on your machine — with all your existing cookies, logins, and extensions. Useful for automating sites where you're already logged in or behind a VPN.
bash
# One command to start Chrome + create a tunnel to Skyvern Cloud
skyvern browser serve --tunnel
Then use the tunnel URL in your task:
python
from skyvern import Skyvern
skyvern = Skyvern(api_key="your-api-key")
task = await skyvern.run_task(
prompt="Download the latest invoice from my account",
browser_address="https://abc123.ngrok-free.dev",
)
WARNING
Always use --api-key when exposing your browser via a tunnel. Without it, anyone with the URL has full control of your browser. See the security docs.
See the full documentation for all options, manual tunnel setup, and troubleshooting.
Get consistent output schema from your run
You can do this by adding the data_extraction_schema parameter:
python
from skyvern import Skyvern
skyvern = Skyvern()
task = await skyvern.run_task(
prompt="Find the top post on hackernews today",
data_extraction_schema={
"type": "object",
"properties": {
"title": {
"type": "string",
"description": "The title of the top post"
},
"url": {
"type": "string",
"description": "The URL of the top post"
},
"points": {
"type": "integer",
"description": "Number of points the post has received"
}
}
}
)
Helpful commands to debug issues
bash
# Launch the Skyvern Server Separately*
skyvern run server
# Launch the Skyvern UI
skyvern run ui
# Check status of the Skyvern service
skyvern status
# Stop the Skyvern service
skyvern stop all
# Stop the Skyvern UI
skyvern stop ui
# Stop the Skyvern Server Separately
skyvern stop server
Performance & Evaluation
Skyvern has SOTA performance on the WebBench benchmark with a 64.4% accuracy. The technical report + evaluation can be found here
Performance on WRITE tasks (eg filling out forms, logging in, downloading files, etc)
Skyvern is the best performing agent on WRITE tasks (eg filling out forms, logging in, downloading files, etc), which is primarily used for RPA (Robotic Process Automation) adjacent tasks.
Skyvern Features
Skyvern Tasks
Tasks are the fundamental building block inside Skyvern. Each task is a single request to Skyvern, instructing it to navigate through a website and accomplish a specific goal.
Tasks require you to specify a url, prompt, and can optionally include a data schema (if you want the output to conform to a specific schema) and error codes (if you want Skyvern to stop running in specific situations).
Skyvern Workflows
Workflows are a way to chain multiple tasks together to form a cohesive unit of work.
For example, if you wanted to download all invoices newer than January 1st, you could create a workflow that first navigated to the invoices page, then filtered down to only show invoices newer than January 1st, extracted a list of all eligible invoices, and iterated through each invoice to download it.
Another example is if you wanted to automate purchasing products from an e-commerce store, you could create a workflow that first navigated to the desired product, then added it to a cart. Second, it would navigate to the cart and validate the cart state. Finally, it would go through the checkout process to purchase the items.
Supported workflow features include:
Browser Task
Browser Action
Data Extraction
Validation
For Loops
File parsing
Sending emails
Text Prompts
HTTP Request Block
Custom Code Block
Uploading files to block storage
(Coming soon) Conditionals
Livestreaming
Skyvern allows you to livestream the viewport of the browser to your local machine so that you can see exactly what Skyvern is doing on the web. This is useful for debugging and understanding how Skyvern is interacting with a website, and intervening when necessary
Form Filling
Skyvern is natively capable of filling out form inputs on websites. Passing in information via the navigation_goal will allow Skyvern to comprehend the information and fill out the form accordingly.
Data Extraction
Skyvern is also capable of extracting data from a website.
You can also specify a data_extraction_schema directly within the main prompt to tell Skyvern exactly what data you'd like to extract from the website, in jsonc format. Skyvern's output will be structured in accordance to the supplied schema.
File Downloading
Skyvern is also capable of downloading files from a website. All downloaded files are automatically uploaded to block storage (if configured), and you can access them via the UI.
Authentication
Skyvern supports a number of different authentication methods to make it easier to automate tasks behind a login. If you'd like to try it out, please reach out to us via email or discord.
🔐 2FA Support (TOTP)
Skyvern supports a number of different 2FA methods to allow you to automate workflows that require 2FA.
We love to see how Skyvern is being used in the wild. Here are some examples of how Skyvern is being used to automate workflows in the real world. Please open PRs to add your own examples!
Run this to create your virtual environment (.venv)
bash
uv sync --group dev
Perform initial server configuration
bash
uv run skyvern quickstart
Navigate to http://localhost:8080 in your browser to start using the UI
The Skyvern CLI supports Windows, WSL, macOS, and Linux environments.
Documentation
More extensive documentation can be found on our 📕 docs page. Please let us know if something is unclear or missing by opening an issue or reaching out to us via email or discord.
Supported LLMs
Provider
Supported Models
OpenAI
GPT-5.5, GPT-5.4, GPT-5, GPT-4.1, o3, o4-mini
Anthropic
Claude 4.7 Opus, Claude 4.6 (Sonnet, Opus), Claude 4.5 (Haiku, Sonnet, Opus)
Azure OpenAI
Any GPT models deployed to your Azure subscription
AWS Bedrock
Claude 4.7, Claude 4.6 (Sonnet, Opus), Claude 4.5 (Sonnet, Opus)
If you want to chat with the skyvern repository to get a high level overview of how it is structured, how to build off it, and how to resolve usage questions, check out Code Sage.
Telemetry
By Default, Skyvern collects basic usage statistics to help us understand how Skyvern is being used. If you would like to opt-out of telemetry, please set the SKYVERN_TELEMETRY environment variable to false.
License
Skyvern's open source repository is supported via a managed cloud. All of the core logic powering Skyvern is available in this open source repository licensed under the AGPL-3.0 License, with the exception of anti-bot measures available in our managed cloud offering.
If you have any questions or concerns around licensing, please contact us and we would be happy to help.