Requirements
Before installing Playwright MCP, ensure you have:- Node.js 18 or newer installed on your system
- An MCP-compatible client (VS Code, Cursor, Claude Desktop, etc.)
On first run, Playwright will automatically download browser binaries. This is a one-time setup that may take a few minutes depending on your connection speed.
Standard Configuration
Most MCP clients use this standard JSON configuration:Client-Specific Installation
Choose your MCP client below for detailed installation instructions:- VS Code
- Cursor
- Claude Desktop
- Windsurf
- Goose
- Cline
VS Code / VS Code Insiders
One-Click Install
Click the button to install directly:Install in VS CodeManual Installation
- Open VS Code Settings
- Search for “MCP”
- Add the standard configuration above
CLI Installation
More Clients
More Clients
Antigravity
Antigravity
Add via Antigravity settings or update your configuration file:
Claude Code
Claude Code
Use the Claude Code CLI:
Codex
Codex
Copilot
Copilot
Interactive Setup
Configuration File
Edit~/.copilot/mcp-config.json:Factory
Factory
CLI
Interactive UI
Type/mcp within Factory droid to open the interactive UI for managing MCP servers.See Factory MCP documentation for more details.Gemini CLI
Gemini CLI
Follow the MCP install guide and use the standard configuration.
Kiro
Kiro
LM Studio
LM Studio
One-Click Install
Install in LM StudioManual Installation
- Open LM Studio
- Go to
Programin the right sidebar - Click
Install→Edit mcp.json - Add the standard configuration
opencode
opencode
Qodo Gen
Qodo Gen
- Open the Qodo Gen chat panel in VSCode or IntelliJ
- Click “Connect more tools”
- Click ”+ Add new MCP”
- Paste the standard configuration
- Click “Save”
Warp
Warp
Settings UI
- Go to
Settings→AI→Manage MCP Servers→+ Add - Follow the add an MCP Server guide
- Use the standard configuration
Slash Command
Type/add-mcp in the Warp prompt and paste:Advanced Installation
Standalone HTTP Server
For systems without a display or when running from IDE worker processes, run Playwright MCP as a standalone HTTP server:Docker Installation
The Docker implementation currently only supports headless Chromium.
MCP Client Spawns Container
Long-Lived Service Container
Run the container as a persistent service:Build Docker Image Locally
Verification
After installation, verify that Playwright MCP is working:- Restart your MCP client to load the new configuration
- Check for available tools - You should see browser automation tools like
browser_navigate,browser_snapshot, etc. - Test basic navigation - Try asking your LLM to navigate to a simple website
Troubleshooting
Browser Not Installed
Browser Not Installed
On first run, Playwright downloads browser binaries automatically. If you see errors about missing browsers:Or use the
browser_install tool from within your MCP client.Permission Issues
Permission Issues
If you encounter permission errors:
- Ensure Node.js is properly installed and in your PATH
- Try running with explicit permissions:
npx --yes @playwright/mcp@latest - On Linux, you may need to install additional dependencies
Connection Timeout
Connection Timeout
If the MCP client can’t connect to Playwright:
- Verify Node.js version is 18 or newer:
node --version - Check that npx can execute:
npx --version - Try increasing timeout in your client config (if supported)
Headless Mode Issues
Headless Mode Issues
If running on a system without a display:
- Use
--headlessflag in your configuration - Or run as a standalone HTTP server (see Advanced Installation)
Next Steps
Quick Start
Create your first automation with Playwright MCP
Configuration
Learn about all configuration options and customization

