How to install Playwright MCP on Cursor

In 2025, Cursor pushed AI beyond passive suggestions into real execution.

Instead of only writing code, AI agents can now run tools, inspect results, and respond in real time.

This shift matters most in test automation, where Playwright MCP enables AI to directly execute and observe Playwright runs.

Traditional Playwright workflows still force constant context switching between writing tests, running them, and debugging failures, slowing feedback and breaking scale.

If you'd rather follow along visually, this video shows the entire setup process.

What is a Playwright?

Playwright is a browser automation framework created by Microsoft to support reliable end-to-end testing across Chromium, Firefox, and WebKit.

It provides stable selectors, auto-waiting, and real browser execution, while engineers still write and maintain the test logic.

That gap is where Playwright MCP comes in, enabling AI to observe execution and provide actionable, context-aware guidance.

What is Playwright MCP?

What is Cursor IDE?

Cursor editor home screen for opening or creating a project.

Cursor is an AI-powered code editor designed to help developers write, understand, and modify code faster. It combines a traditional editor with built-in AI that can reason over your codebase and execute tasks directly from context.

Let's start the Setup process.

How to Install Playwright MCP on Cursor

Before you begin, ensure Node.js and npm are installed and functioning correctly.

There are two ways to set up Playwright MCP in Cursor IDE, depending on how much control you want over the process.

Method 1. Quick Playwright MCP Setup

For the fastest setup in Cursor, use the quick setup option.

Just hit the "Add Playwright MCP to Cursor" button.

That's it. Done in seconds. You can skim to verify the installation

If the link gives you trouble or you'd rather do things yourself, check out this second method for a step-by-step guide.

Method 2. Manual Playwright MCP Setup

If you prefer more control or want to understand exactly how the integration works, follow the manual setup process below.

Step 1. Install MCP Server Package

Open the Cursor and run this command in the Cursor's terminal to install Playwright MCP.

npm install @playwright/mcp --save-dev

The --save-dev flag adds Playwright MCP as a development dependency, since it is only needed during local testing and AI-assisted development, not in production builds.

Step 2. Update Cursor Configuration

Here you configure Cursor to launch the Playwright MCP server. You can apply it to the current project or globally across all projects.

Approach A: Project Specific Configuration

This method keeps your configuration contained within your project directory, which is ideal for team environments or when you use different tools in different projects.

1. Locate the Configuration File: Inside the root of your project directory, create or navigate to the .cursor folder.

2. Create mcp.json: Create a file named mcp.json inside the .cursor folder. Your project structure should look like this.

your-project/
├── .cursor/
│   └── mcp.json
├── tests/
└── package.json

3. Add the Configuration: Paste the following JSON structure into the file.

// Add this to the mcp.json file
{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}

This tells Cursor to execute the installed Playwright MCP server using npx.

Approach B: Global configuration

This approach registers the Playwright MCP tool directly within Cursor's general settings.

1. Open Cursor Settings.

2. Navigate to Tools & MCP tab.

3. Add a New Server. Click "Add Custom MCP", then just paste the JSON payload straight into the box.

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}

Step 3. Restart & Verify Connection

Now, let's verify integration.

• Open Cursor Settings.
• Go to Tools & MCP.
• Confirm that Playwright MCP appears in the list.

If it's listed, the configuration is working.

Step 4. Run a Real Browser Automation Example

You can validate the connection by running a full login flow on app.testdino.com with screenshots and logout.

Use the Cursor chat panel and run a prompt like this:

"Open app.testdino.com, log in using the email, capture a screenshot after login, log out, and capture another screenshot. Then generate the correct Playwright test script for this flow."

Expected output

• Cursor opens app.testdino.com in a real browser

• Logs in using email

• Captures a screenshot after login

• Logs out of the application

• Captures a screenshot after logout

• Generates a ready-to-use Playwright test script for the entire flow

Once your setup is validated and stable, you can move beyond basic navigation and explore advanced Playwright MCP workflows like multi-page flows, conditional actions, and data-driven testing.

Common Issues and Troubleshooting

Take a look at this troubleshooting guide. It'll help you fix common issues that may occur while installing Playwright MCP in Cursor.

Tests Are Easy Now

The challenge isn't creating tests anymore. It's knowing what broke, when, and why.

Try TestDino Try TestDino

Conclusion

The setup is complete. It's time to activate the AI and have the tests written directly into the editor for a massive efficiency increase.

Suddenly, you're not wasting hours setting things up, jumping between apps, or playing hide-and-seek with bugs.

Add in neat test reports and smarter ways to figure out what went wrong, like what TestDino brings to the table, and getting feedback becomes way faster and a lot less confusing.

Want the full setup walkthrough? I've documented everything in my complete Playwright MCP guide from installation to advanced workflows.

FAQs

Pratik Patel

Founder & CEO

Pratik Patel is the founder of TestDino, a Playwright-focused observability and CI optimization platform that helps engineering and QA teams gain clear visibility into automated test results, flaky failures, and CI pipeline health. With 12+ years of QA automation experience, he has worked closely with startups and enterprise organizations to build and scale high-performing QA teams, including companies such as Scotts Miracle-Gro, Avenue One, and Huma.

Pratik is an active contributor to the open-source community and a member of the Test Tribe community. He previously authored Make the Move to Automation with Appium and supported lot of QA engineers with practical tools, consulting, and educational resources, and he regularly writes about modern testing practices, Playwright, and developer productivity.

View all posts →