Playwright MCP Server
This server provides browser automation capabilities using Playwright, allowing LLMs to interact with web pages through structured accessibility snapshots. It enables tasks like web navigation, form filling, and data extraction without the need for screenshots or vision-tuned models.
README
Playwright MCP Server
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.
About this MCP Server: To understand how to connect to and utilize this MCP server, you can refer to the official Model Context Protocol documentation at mcp.apify.com.
Connection URL
MCP clients can connect to this server at:
https://jiri-spilka--playwright-mcp-server.apify.actor/mcp
Client Configuration
To connect to this MCP server, use the following configuration in your MCP client:
{
"mcpServers": {
"playwright": {
"url": "https://jiri-spilka--playwright-mcp-server.apify.actor/mcp",
"headers": {
"Authorization": "Bearer YOUR_APIFY_TOKEN"
}
}
}
}
Note: Replace YOUR_APIFY_TOKEN with your actual Apify API token. You can find your token in the Apify Console.
Links
- GitHub Repository: https://github.com/microsoft/playwright-mcp
- Actor Repository: https://github.com/apify/actor-playwright-mcp
- Apify MCP Documentation: https://mcp.apify.com
๐ฉ Claim this MCP server
All credits to the original authors of https://github.com/microsoft/playwright-mcp To claim this server, please write to ai@apify.com.
Key features
- ๐ Uses Playwright's accessibility tree instead of pixel-based input for faster, lighter operation
- ๐ Works with structured data only - no vision models required
- ๐ฏ Applies tools deterministically, avoiding the ambiguity of screenshot approaches
- ๐ Supports Apify Proxy (datacenter, residential, custom) and other Apify features
Use cases
- ๐ Web navigation and form filling
- ๐ Structured data extraction
- ๐งช LLM-driven automated testing
- ๐ค Browser automation for AI agents
Tools (source)
Tools
<!--- Tools generated by update-readme.js -->
<details> <summary><b>Core automation</b></summary>
<!-- NOTE: This has been generated via update-readme.js -->
- browser_click
- Title: Click
- Description: Perform click on a web page
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementref(string): Exact target element reference from the page snapshotdoubleClick(boolean, optional): Whether to perform a double click instead of a single clickbutton(string, optional): Button to click, defaults to left
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_close
- Title: Close browser
- Description: Close the page
- Parameters: None
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_console_messages
- Title: Get console messages
- Description: Returns all console messages
- Parameters: None
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_drag
- Title: Drag mouse
- Description: Perform drag and drop between two elements
- Parameters:
startElement(string): Human-readable source element description used to obtain the permission to interact with the elementstartRef(string): Exact source element reference from the page snapshotendElement(string): Human-readable target element description used to obtain the permission to interact with the elementendRef(string): Exact target element reference from the page snapshot
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_evaluate
- Title: Evaluate JavaScript
- Description: Evaluate JavaScript expression on page or element
- Parameters:
function(string): () => { /* code / } or (element) => { / code */ } when element is providedelement(string, optional): Human-readable element description used to obtain permission to interact with the elementref(string, optional): Exact target element reference from the page snapshot
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_file_upload
- Title: Upload files
- Description: Upload one or multiple files
- Parameters:
paths(array): The absolute paths to the files to upload. Can be a single file or multiple files.
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_fill_form
- Title: Fill form
- Description: Fill multiple form fields
- Parameters:
fields(array): Fields to fill in
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_handle_dialog
- Title: Handle a dialog
- Description: Handle a dialog
- Parameters:
accept(boolean): Whether to accept the dialog.promptText(string, optional): The text of the prompt in case of a prompt dialog.
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_hover
- Title: Hover mouse
- Description: Hover over element on page
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementref(string): Exact target element reference from the page snapshot
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_navigate
- Title: Navigate to a URL
- Description: Navigate to a URL
- Parameters:
url(string): The URL to navigate to
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_navigate_back
- Title: Go back
- Description: Go back to the previous page
- Parameters: None
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_network_requests
- Title: List network requests
- Description: Returns all network requests since loading the page
- Parameters: None
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_press_key
- Title: Press a key
- Description: Press a key on the keyboard
- Parameters:
key(string): Name of the key to press or a character to generate, such asArrowLeftora
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_resize
- Title: Resize browser window
- Description: Resize the browser window
- Parameters:
width(number): Width of the browser windowheight(number): Height of the browser window
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_select_option
- Title: Select option
- Description: Select an option in a dropdown
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementref(string): Exact target element reference from the page snapshotvalues(array): Array of values to select in the dropdown. This can be a single value or multiple values.
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_snapshot
- Title: Page snapshot
- Description: Capture accessibility snapshot of the current page, this is better than screenshot
- Parameters: None
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_take_screenshot
- Title: Take a screenshot
- Description: Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.
- 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.element(string, optional): Human-readable element description used to obtain permission to screenshot the element. If not provided, the screenshot will be taken of viewport. If element is provided, ref must be provided too.ref(string, optional): Exact target element reference from the page snapshot. If not provided, the screenshot will be taken of viewport. If ref is provided, element must be provided too.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.
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_type
- Title: Type text
- Description: Type text into editable element
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementref(string): Exact target element reference from the page snapshottext(string): Text to type into the elementsubmit(boolean, optional): Whether to submit entered text (press Enter after)slowly(boolean, optional): Whether to type one character at a time. Useful for triggering key handlers in the page. By default entire text is filled in at once.
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_wait_for
- Title: Wait for
- Description: Wait for text to appear or disappear or a specified time to pass
- Parameters:
time(number, optional): The time to wait in secondstext(string, optional): The text to wait fortextGone(string, optional): The text to wait for to disappear
- Read-only: true
</details>
<details> <summary><b>Tab management</b></summary>
<!-- NOTE: This has been generated via update-readme.js -->
- browser_tabs
- Title: Manage tabs
- Description: List, create, close, or select a browser tab.
- Parameters:
action(string): Operation to performindex(number, optional): Tab index, used for close/select. If omitted for close, current tab is closed.
- Read-only: false
</details>
<details> <summary><b>Browser installation</b></summary>
<!-- NOTE: This has been generated via update-readme.js -->
- 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
</details>
<details> <summary><b>Coordinate-based (opt-in via --caps=vision)</b></summary>
<!-- NOTE: This has been generated via update-readme.js -->
- browser_mouse_click_xy
- Title: Click
- Description: Click left mouse button at a given position
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementx(number): X coordinatey(number): Y coordinate
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_mouse_drag_xy
- Title: Drag mouse
- Description: Drag left mouse button to a given position
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementstartX(number): Start X coordinatestartY(number): Start Y coordinateendX(number): End X coordinateendY(number): End Y coordinate
- Read-only: false
<!-- NOTE: This has been generated via update-readme.js -->
- browser_mouse_move_xy
- Title: Move mouse
- Description: Move mouse to a given position
- Parameters:
element(string): Human-readable element description used to obtain permission to interact with the elementx(number): X coordinatey(number): Y coordinate
- Read-only: true
</details>
<details> <summary><b>PDF generation (opt-in via --caps=pdf)</b></summary>
<!-- NOTE: This has been generated via update-readme.js -->
- 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
</details>
<details> <summary><b>Verify (opt-in via --caps=verify)</b></summary>
<!-- NOTE: This has been generated via update-readme.js -->
- browser_verify_element_visible
- Title: Verify element visible
- Description: Verify element is visible on the page
- Parameters:
role(string): ROLE of the element. Can be found in the snapshot like this:- {ROLE} "Accessible Name":accessibleName(string): ACCESSIBLE_NAME of the element. Can be found in the snapshot like this:- role "{ACCESSIBLE_NAME}"
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_verify_list_visible
- Title: Verify list visible
- Description: Verify list is visible on the page
- Parameters:
element(string): Human-readable list descriptionref(string): Exact target element reference that points to the listitems(array): Items to verify
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_verify_text_visible
- Title: Verify text visible
- Description: Verify text is visible on the page. Prefer browser_verify_element_visible if possible.
- Parameters:
text(string): TEXT to verify. Can be found in the snapshot like this:- role "Accessible Name": {TEXT}or like this:- text: {TEXT}
- Read-only: true
<!-- NOTE: This has been generated via update-readme.js -->
- browser_verify_value
- Title: Verify value
- Description: Verify element value
- Parameters:
type(string): Type of the elementelement(string): Human-readable element descriptionref(string): Exact target element reference that points to the elementvalue(string): Value to verify. For checkbox, use "true" or "false".
- Read-only: true
</details>
<!--- End of tools generated section -->
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.