Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fast Playwright MCPgo to github.com and show me just the trending repositories section"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fast Playwright MCP
This MCP server is a fork of the Microsoft one. https://github.com/microsoft/playwright-mcp
A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.
Key Features
Fast and lightweight. Uses Playwright's accessibility tree, not pixel-based input.
LLM-friendly. No vision models needed, operates purely on structured data.
Deterministic tool application. Avoids ambiguity common with screenshot-based approaches.
Fast Server Features (This Fork)
Token Optimization. All tools support an
expectationparameter to control response content:includeCode: false- Suppress Playwright code generation to reduce tokensincludeSnapshot: false- Skip page snapshot for minimal responses (70-80% token reduction)includeConsole: false- Exclude console messagesincludeTabs: false- Hide tab information
Image Compression. Screenshot tool supports
imageOptions:format: 'jpeg'- Use JPEG instead of PNGquality: 1-100- Compress images (e.g., 50 for 50% quality)maxWidth: number- Resize images to max width
Batch Execution. Use
browser_batch_executefor multiple operations:Significant token reduction by eliminating redundant responses
Per-step and global expectation configuration
Error handling with
continueOnErrorandstopOnFirstErroroptions
Snapshot Control. Limit snapshot size with
snapshotOptions:selector: string- Capture only specific page sections (recommended over maxLength)format: "aria"- Accessibility tree format for LLM processing
Diff Detection. Track only changes with
diffOptions:enabled: true- Show only what changed from previous state (massive token saver)format: "minimal"- Ultra-compact diff outputPerfect for monitoring state changes during navigation or interactions
Diagnostic System. Advanced debugging and element discovery tools:
browser_find_elements- Find elements using multiple search criteria (text, role, attributes)browser_diagnose- Comprehensive page analysis with performance metrics and troubleshootingEnhanced error handling with alternative element suggestions
Page structure analysis (iframes, modals, accessibility metrics)
Performance monitoring with execution time under 300ms
Enhanced Selector System. Unified element selection with multiple strategies:
Selector Arrays: All element-based tools now support multiple selectors with automatic fallback
4 Selector Types:
ref: System-generated element IDs from previous tool results (highest priority)role: ARIA roles with optional text matching (e.g.,{role: "button", text: "Submit"})css: Standard CSS selectors (e.g.,{css: "#submit-btn"})text: Text content search with optional tag filtering (e.g.,{text: "Click me", tag: "button"})
Intelligent Resolution: Parallel CSS resolution, sequential role matching, automatic fallback
Multiple Match Handling: When multiple elements match, returns candidate list for LLM selection
HTML Inspection: New
browser_inspect_htmltool for intelligent content extraction with depth control
Requirements
Node.js 18 or newer
VS Code, Cursor, Windsurf, Claude Desktop, Goose or any other MCP client
Getting started
First, install the Playwright MCP server with your client.
Standard config works in most of the tools:
Use the Claude Code CLI to add the Playwright MCP server:
Follow the MCP install guide, use the standard config above.
Click the button to install:
Or install manually:
Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, use command type with the command npx @tontoko/fast-playwright-mcp@latest. You can also verify config or add command like arguments via clicking Edit.
Follow the MCP install guide, use the standard config above.
Click the button to install:
Or install manually:
Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to npx @tontoko/fast-playwright-mcp. Click "Add Extension".
Click the button to install:
Or install manually:
Go to Program in the right sidebar -> Install -> Edit mcp.json. Use the standard config above.
Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:
Open Qodo Gen chat panel in VSCode or IntelliJ → Connect more tools → + Add new MCP → Paste the standard config above.
Click Save.
Click the button to install:
Or install manually:
Follow the MCP install guide, use the standard config above. You can also install the Playwright MCP server using the VS Code CLI:
After installation, the Playwright MCP server will be available for use with your GitHub Copilot agent in VS Code.
Follow Windsurf MCP documentation. Use the standard config above.
Configuration
Playwright MCP server supports following arguments. They can be provided in the JSON configuration above, as a part of the "args" list:
User profile
You can run Playwright MCP with persistent profile like a regular browser (default), in isolated contexts for testing sessions, or connect to your existing browser using the browser extension.
Persistent profile
All the logged in information will be stored in the persistent profile, you can delete it between sessions if you'd like to clear the offline state.
Persistent profile is located at the following locations and you can override it with the --user-data-dir argument.
Isolated
In the isolated mode, each session is started in the isolated profile. Every time you ask MCP to close the browser,
the session is closed and all the storage state for this session is lost. You can provide initial storage state
to the browser via the config's contextOptions or via the --storage-state argument. Learn more about the storage
state here.
Browser Extension
The Playwright MCP Chrome Extension allows you to connect to existing browser tabs and leverage your logged-in sessions and browser state. See extension/README.md for installation and setup instructions.
Configuration file
The Playwright MCP server can be configured using a JSON configuration file. You can specify the configuration file
using the --config command line option:
Standalone MCP server
When running headed browser on system w/o display or from worker processes of the IDEs,
run the MCP server from environment with the DISPLAY and pass the --port flag to enable HTTP transport.
And then in MCP client config, set the url to the HTTP endpoint:
NOTE: The Docker implementation only supports headless chromium at the moment.
You can build the Docker image yourself.
Tools
browser_batch_execute
Title: Batch Execute Browser Actions
Description: Execute multiple browser actions in sequence. PREFER over individual tools for 2+ operations.
Parameters:
steps(array): Array of steps to execute in sequence. Recommended for form filling (multiple type→click), multi-step navigation, any workflow with 2+ known steps. Saves 90% tokens vs individual calls. Example: [{tool:"browser_navigate",arguments:{url:"https://example.com"}},{tool:"browser_type",arguments:{selectors:[{css:"#user"}],text:"john"}},{tool:"browser_click",arguments:{selectors:[{css:"#btn"}]}}]stopOnFirstError(boolean, optional): Stop entire batch on first errorglobalExpectation(optional): Default expectation for all steps. Recommended: {includeSnapshot:false,snapshotOptions:{selector:"#app"},diffOptions:{enabled:true}}. Per-step override with steps[].expectation
Read-only: false
browser_click
Title: Perform click on web page
Description: Perform click on web page
Parameters:
selectors(array): Array of element selectors (max 5). Selectors are tried in order until one succeeds (fallback mechanism). Multiple matches trigger an error with candidate list. Supports: ref (highest priority), CSS (#id, .class, tag), role (button, textbox, etc.), text content. Example: [{css: "#submit"}, {role: "button", text: "Submit"}] - tries ID first, falls back to role+textdoubleClick(boolean, optional): Double-click if truebutton(string, optional): Mouse button (default: left)expectation(object, optional): Page state capture config. Use batch_execute for multi-clicks
Read-only: false
browser_close
Title: Close browser
Description: Close the page
Parameters: None
Read-only: true
browser_console_messages
Title: Get console messages
Description: Returns all console messages
Parameters:
consoleOptions(object, optional): undefined
Read-only: true
browser_diagnose
Title: Diagnose page
Description: Analyze page complexity and performance characteristics. Reports on: iframe count, DOM size, modal states, element statistics. Use for: debugging slow pages, understanding page structure, or monitoring page complexity.
Parameters:
searchForElements(object, optional): Search for specific elements and include them in the reportincludePerformanceMetrics(boolean, optional): Include performance metrics in the reportincludeAccessibilityInfo(boolean, optional): Include accessibility informationincludeTroubleshootingSuggestions(boolean, optional): Include troubleshooting suggestionsdiagnosticLevel(string, optional): Level of diagnostic detail: none (no diagnostics), basic (critical only), standard (default), detailed (with metrics), full (all info)useParallelAnalysis(boolean, optional): Use Phase 2 parallel analysis for improved performance and resource monitoringuseUnifiedSystem(boolean, optional): Use Phase 3 unified diagnostic system with enhanced error handling and monitoringconfigOverrides(object, optional): Runtime configuration overrides for diagnostic systemincludeSystemStats(boolean, optional): Include unified system statistics and health informationexpectation(object, optional): undefined
Read-only: true
browser_drag
Title: Drag mouse
Description: Perform drag and drop between two elements
Parameters:
startSelectors(array): Source element selectors for drag startendSelectors(array): Target element selectors for drag endexpectation(object, optional): Page state after drag. Use batch_execute for workflows
Read-only: false
browser_evaluate
Title: Evaluate JavaScript
Description: Evaluate JavaScript expression on page or element and return result
Parameters:
function(string): JS function: () => {...} or (element) => {...}selectors(array, optional): Optional element selectors. If provided, function receives element as parameterexpectation(object, optional): Page state config. false for data extraction, true for DOM changes
Read-only: false
browser_file_upload
Title: Upload files
Description: Upload one or multiple files to file input
Parameters:
paths(array): Absolute paths to upload (array)expectation(object, optional): Page state config. Use batch_execute for click→upload
Read-only: false
browser_find_elements
Title: Find elements
Description: Find elements on the page using multiple search criteria such as text, role, tag name, or attributes. Returns matching elements sorted by confidence.
Parameters:
searchCriteria(object): Search criteria for finding elementsmaxResults(number, optional): Maximum number of results to returnincludeDiagnosticInfo(boolean, optional): Include diagnostic information about the pageuseUnifiedSystem(boolean, optional): Use unified diagnostic system for enhanced error handlingenableEnhancedDiscovery(boolean, optional): Enable enhanced element discovery with contextual suggestionsperformanceThreshold(number, optional): Performance threshold in milliseconds for element discoveryexpectation(object, optional): undefined
Read-only: true
browser_handle_dialog
Title: Handle a dialog
Description: Handle a dialog (alert, confirm, prompt)
Parameters:
accept(boolean): Accept (true) or dismiss (false)promptText(string, optional): Text for prompt dialogsexpectation(object, optional): Page state after dialog. Use batch_execute for workflows
Read-only: false
browser_hover
Title: Hover mouse
Description: Hover over element on page
Parameters:
selectors(array): Array of element selectors (max 5). Selectors are tried in order until one succeeds (fallback mechanism). Multiple matches trigger an error with candidate list. Supports: ref (highest priority), CSS (#id, .class, tag), role (button, textbox, etc.), text content. Example: [{css: "#submit"}, {role: "button", text: "Submit"}] - tries ID first, falls back to role+textexpectation(object, optional): Page state after hover. Use batch_execute for hover→click
Read-only: true
browser_inspect_html
Title: HTML inspection
Description: Extract and analyze HTML content from web pages with intelligent filtering and size control. Optimized for LLM consumption with configurable depth, format options, and automatic truncation.
Parameters:
selectors(array): Array of element selectors to inspectdepth(number, optional): Maximum hierarchy depth to extractincludeStyles(boolean, optional): Include computed CSS stylesmaxSize(number, optional): Maximum size in bytes (1KB-500KB)format(string, optional): Output formatincludeAttributes(boolean, optional): Include element attributespreserveWhitespace(boolean, optional): Preserve whitespace in contentexcludeSelector(string, optional): CSS selector to exclude elementsincludeSuggestions(boolean, optional): Include CSS selector suggestions in outputincludeChildren(boolean, optional): Include child elements in extractionoptimizeForLLM(boolean, optional): Optimize extracted HTML for LLM consumptionexpectation(object, optional): Page state config (minimal for HTML inspection)
Read-only: true
browser_navigate
Title: Navigate to a URL
Description: Navigate to a URL
Parameters:
url(string): The URL to navigate toexpectation(object, optional): Page state after navigation
Read-only: false
browser_navigate_back
Title: Go back to previous page
Description: Go back to previous page
Parameters:
expectation(object, optional): Page state after going back
Read-only: true
browser_navigate_forward
Title: Go forward to next page
Description: Go forward to next page
Parameters:
expectation(object, optional): Page state after going forward
Read-only: true
browser_network_requests
Title: List network requests
Description: Returns network requests since loading the page with optional filtering
Parameters:
urlPatterns(array, optional): URL patterns to filter (supports regex)excludeUrlPatterns(array, optional): URL patterns to exclude (takes precedence)statusRanges(array, optional): Status code ranges (e.g., [{min:200,max:299}])methods(array, optional): HTTP methods to filtermaxRequests(number, optional): Max requests to return (default: 20)newestFirst(boolean, optional): Order by timestamp (default: newest first)
Read-only: true
browser_press_key
Title: Press a key
Description: Press a key on the keyboard
Parameters:
key(string): Key to pressexpectation(object, optional): Page state config. Use batch_execute for multiple keys
Read-only: false
browser_resize
Title: Resize browser window
Description: Resize the browser window
Parameters:
width(number): Width of the browser windowheight(number): Height of the browser windowexpectation(object, optional): undefined
Read-only: true
browser_select_option
Title: Select option
Description: Select option in dropdown
Parameters:
selectors(array): Array of element selectors (max 5). Selectors are tried in order until one succeeds (fallback mechanism). Multiple matches trigger an error with candidate list. Supports: ref (highest priority), CSS (#id, .class, tag), role (button, textbox, etc.), text content. Example: [{css: "#submit"}, {role: "button", text: "Submit"}] - tries ID first, falls back to role+textvalues(array): Values to select (array)expectation(object, optional): Page state after selection. Use batch_execute for forms
Read-only: false
browser_snapshot
Title: Page snapshot
Description: Capture accessibility snapshot of current page
Parameters:
expectation(object, optional): Page state config
Read-only: true
browser_take_screenshot
Title: Take a screenshot
Description: Take a screenshot of current page and return image data
Parameters:
type(string, optional): Image format for the screenshot. Default is png.filename(string, optional): File name to save the screenshot to. Defaults topage-{timestamp}.{png|jpeg}if not specified.selectors(array, optional): Optional element selectors for element screenshots. If not provided, viewport screenshot will be taken.fullPage(boolean, optional): When true, takes a screenshot of the full scrollable page, instead of the currently visible viewport. Cannot be used with element screenshots.expectation(object, optional): Additional page state config
Read-only: true
browser_type
Title: Type text
Description: Type text into editable element
Parameters:
selectors(array): Array of element selectors (max 5) supporting ref, role, CSS, or text-based selectiontext(string): Text to type into the elementsubmit(boolean, optional): Press Enter after typing if trueslowly(boolean, optional): Type slowly for auto-complete if trueexpectation(object, optional): Page state config. Use batch_execute for forms
Read-only: false
browser_wait_for
Title: Wait for
Description: Wait for text to appear or disappear or a specified time to pass
Parameters:
time(number, optional): Wait time in secondstext(string, optional): undefinedtextGone(string, optional): undefinedexpectation(object, optional): Page state after wait
Read-only: true
browser_tab_close
Title: Close a tab
Description: Close a tab by index or close current tab
Parameters:
index(number, optional): Tab index to close (omit for current)expectation(object, optional): Page state after close
Read-only: false
browser_tab_list
Title: List tabs
Description: List browser tabs with titles and URLs
Parameters:
expectation(object, optional): Page state config
Read-only: true
browser_tab_new
Title: Open a new tab
Description: Open a new tab
Parameters:
url(string, optional): URL for new tab (optional)expectation(object, optional): Page state of new tab
Read-only: true
browser_tab_select
Title: Select a tab
Description: Select a tab by index
Parameters:
index(number): The index of the tab to selectexpectation(object, optional): Page state after tab switch
Read-only: true
browser_install
Title: Install the browser specified in the config
Description: Install the browser specified in the config. Call this if you get an error about the browser not being installed.
Parameters: None
Read-only: false
browser_mouse_click_xy
Title: Click
Description: Click at specific coordinates
Parameters:
element(string): undefinedx(number): X coordinate (requires --caps=vision)y(number): Y coordinate (requires --caps=vision)expectation(object, optional): Page state after click. Prefer element ref over coords
Read-only: false
browser_mouse_drag_xy
Title: Drag mouse
Description: Drag from one coordinate to another
Parameters:
element(string): undefinedstartX(number): Start X (requires --caps=vision)startY(number): Start Y (requires --caps=vision)endX(number): End XendY(number): End Yexpectation(object, optional): Page state after drag. Prefer element refs over coords
Read-only: false
browser_mouse_move_xy
Title: Move mouse
Description: Move mouse to specific coordinates.Requires --caps=vision.x,y:coordinates.expectation:{includeSnapshot:false} for simple move,true to see hover effects.PREFER element-based interactions over coordinates when possible.
Parameters:
element(string): undefinedx(number): X coordinatey(number): Y coordinateexpectation(object, optional): undefined
Read-only: true
browser_pdf_save
Title: Save as PDF
Description: Save page as PDF
Parameters:
filename(string, optional): File name to save the pdf to. Defaults topage-{timestamp}.pdfif not specified.
Read-only: true
Token Optimization Features
Playwright MCP server includes advanced token optimization features to reduce token usage and improve performance through response filtering and batch execution.
Response Filtering with Expectation Parameter
All browser tools support an optional expectation parameter that controls what information is included in the response. This can significantly reduce token usage by excluding unnecessary data.
Basic Usage
Expectation Options
includeSnapshot(boolean, default: varies by tool): Include page accessibility snapshotincludeConsole(boolean, default: varies by tool): Include browser console messagesincludeDownloads(boolean, default: true): Include download informationincludeTabs(boolean, default: varies by tool): Include tab informationincludeCode(boolean, default: true): Include executed code in response
Advanced Snapshot Options
Console Filtering Options
Batch Execution
Execute multiple browser actions in a single request with optimized response handling and flexible error control.
Basic Batch Execution
Advanced Batch Configuration
Error Handling Options
continueOnError(per step): Continue batch execution even if this step failsstopOnFirstError(global): Stop entire batch on first errorFlexible combination allows for robust automation workflows
Tool-Specific Defaults
Each tool has optimized defaults based on typical usage patterns:
Navigation tools (
browser_navigate): Include full context for verificationInteractive tools (
browser_click,browser_type): Include snapshot but minimal loggingScreenshot/snapshot tools: Exclude additional context
Code evaluation: Include console output but minimal other info
Wait operations: Minimal output for efficiency
Performance Benefits
Token Reduction: 50-80% reduction in token usage with optimized expectations
Faster Execution: 2-5x speed improvement with batch execution
Reduced Latency: Fewer round trips between client and server
Cost Optimization: Lower API costs due to reduced token consumption
Response Diff Detection
The Fast Server includes automatic diff detection to efficiently track changes between consecutive tool executions:
Diff Detection Benefits
Minimal token usage: Only changed content is shown instead of full snapshots
Change tracking: Automatically detects what changed after actions
Flexible formats: Choose between unified, split, or minimal diff formats
Smart caching: Compares against previous response from the same tool
When to Use Diff Detection
UI interactions without navigation: Clicks, typing, hover effects
Dynamic content updates: Loading more items, real-time updates
Form interactions: Track changes as users fill forms
Selective monitoring: Use with CSS selectors to track specific areas
Best Practices
Use batch execution for multi-step workflows
Enable diff detection for actions without page navigation
Disable snapshots for intermediate steps that don't need verification
Use selective snapshots with CSS selectors for large pages
Filter console messages to relevant levels only
Combine global and step-specific expectations for fine-grained control
Use minimal diff format for maximum token savings
Diagnostic System Examples
Find alternative elements when selectors fail:
Generate comprehensive page diagnostics:
Debug automation failures with enhanced errors: All tools automatically provide enhanced error messages with:
Alternative element suggestions
Page structure analysis
Context-aware troubleshooting tips
Performance insights
Network Request Filtering
The browser_network_requests tool provides advanced filtering capabilities to reduce token usage by up to 80-95% when working with network logs.
Basic Usage Examples
Advanced Filtering
Regex Pattern Support
Token Optimization Benefits
Massive reduction: 80-95% fewer tokens for large applications
Focused debugging: See only relevant network activity
Performance monitoring: Track specific endpoints or error patterns
Cost savings: Lower API costs due to reduced token usage
When to Use Network Filtering
API debugging: Focus on specific endpoints and methods
Error monitoring: Track only failed requests
Performance analysis: Monitor slow or problematic endpoints
Large applications: Reduce overwhelming network logs
Token management: Stay within LLM context limits
Migration Guide
Existing code continues to work without changes. To optimize:
Start by adding
expectation: { includeSnapshot: false }to intermediate stepsUse batch execution for sequences of 3+ operations
Gradually fine-tune expectations based on your specific needs
Use diagnostic tools when automation fails or needs debugging