browser-automationdeveloper-tools

Playwright Recorder

ashish-bansal

by ashish-bansal

Streamline browser automation with Playwright MCP. Capture interactions, screenshots, and generate test scripts for effi

Playwright MCP enables browser automation and interaction recording by capturing DOM interactions, screenshots, and page navigation events to generate reproducible test scripts through a visual, context-driven workflow.

github stars

29

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

AI generates working selectors from real DOMVisual context for better test accuracyRecords interactions into reproducible scripts

best for

  • / Developers writing browser automation tests
  • / QA engineers creating end-to-end test suites
  • / Teams debugging web application workflows

capabilities

  • / Initialize browsers with specific URLs
  • / Capture full-page screenshots
  • / Extract complete DOM structure and context
  • / Execute custom JavaScript code in browser
  • / Record user interactions into test scripts

what it does

Provides AI assistants with real-time browser access to generate accurate Playwright test scripts by capturing DOM interactions, screenshots, and page context.

about

Playwright Recorder is a community-built MCP server published by ashish-bansal that provides AI assistants with tools and capabilities via the Model Context Protocol. Streamline browser automation with Playwright MCP. Capture interactions, screenshots, and generate test scripts for effi It is categorized under browser automation, developer tools. This server exposes 5 tools that AI clients can invoke during conversations and coding sessions.

how to install

You can install Playwright Recorder in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

NOASSERTION

Playwright Recorder is released under the NOASSERTION license.

readme

How to Use playwright-mcp?

npm version Docs

Introduction

Ever tried using Cursor or Claude to write Playwright tests? Yeah, it's kind of a mess.

Why? Because your AI assistant has no clue what's on your web page. It's like trying to describe a painting to someone who's blindfolded. The result?

  • Flaky tests → The AI is guessing selectors, and it gets them wrong.
  • Broken scripts → You spend more time fixing tests than writing them.
  • Debugging nightmares → The AI can't "see" what's happening, so you end up doing all the heavy lifting.

Wouldn't it be nice if your AI could actually understand your web page instead of just making educated guesses?

Enter playwright-mcp !

playwright-mcp gives your AI assistant superpowers by making the browser fully visible to it. Instead of working in the dark, your AI assistant now has real-time access to the page DOM, elements, and interactions.

How playwright-mcp Works (AKA How We Fix This Mess)

Once installed, playwright-mcp spins up a Playwright-controlled browser and gives your AI assistant full access to it. This unlocks:

  1. Recording interactions → Click, type, scroll—let playwright-mcp turn your actions into fully functional Playwright test cases.
  2. Taking screenshots → Capture elements or full pages so your AI gets actual visual context (no more guessing).
  3. Extracting the DOM → Grab the entire HTML structure so the AI can generate rock-solid selectors.
  4. Executing JavaScript → Run custom JS inside the browser for debugging, automation, or just for fun.

Why You'll Love playwright-mcp

🚀 AI-generated tests that actually work → No more flaky selectors, broken tests, or guesswork.

Massive time savings → Write and debug Playwright tests 5x faster.

🛠️ Fewer headaches → Your AI assistant gets live page context, so it can generate real test cases.

🔌 Works out of the box → Plug it into Cursor, Claude, WindSurf, or whatever you use—it just works.

Give Your AI the Context It Deserves

Tired of fixing AI-generated tests? Stop debugging AI's bad guesses—start writing flawless Playwright tests. Use the guide below to install playwright-mcp and let your AI assistant actually help you for once.


Installation: Get Up and Running in No Time

Prerequisites (a.k.a. What You Need Before You Start)

Before you install playwright-mcp, make sure you have:

✅ Node.js installed on your system (because, well… it's an npm package)

✅ Playwright and its Chromium browser installed

✅ An IDE that supports MCP, like Cursor

✅ A brain that's ready to automate Playwright tests like a pro

Setting Up playwright-mcp (It's Easy, I Promise)

Connect It to Your IDE (Cursor Setup)

If you're using Cursor, follow these steps to connect playwright-mcp like a boss:

  1. Open Cursor IDE

  2. Navigate to Settings (⚙️)

  3. Select Cursor Settings → Go to the MCP tab

  4. Click "Add new MCP server"

  5. Fill in the following details:

    Connect playwright-mcp to cursor

    • Name → playwright-mcp
    • Command → npx -y playwright-mcp
  6. Click "Add", and boom—you're connected! 🚀

Note: If clicking on "Add new MCP server", opens a file(.cursor/mcp.json), Paste the following code and save:

{
  "mcpServers": {
    "playwright-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-mcp"
      ]
    }
  }
}

Now Cursor actually understands your web pages. No more random test suggestions based on zero context! Head to the Claude tutorial or Cursor tutorial to understand it in details.


Connect It to Claude desktop

Wait… Does It Work with Other AI Assistants? Yes! While playwright-mcp is a match made in heaven for IDEs, you can use it with Claude desktop to write tests as well.

  1. Install playwright-mcp (The Easy Part)

    1. First things first, fire up your terminal and run:
    2. npm install -g playwright-mcp
  2. Hook It Up to Claude Desktop

    1. Find the Configuration File
    2. On windows
      1. %APPDATA%\Claude\claude_desktop_config.json
    3. On macOS:
      1. ~/Library/Application Support/Claude/claude_desktop_config.json
    4. Update the config file
    {
      "mcpServers": {
        "playwright": {
          "command": "npx",
          "args": ["-y", "playwright-mcp"]
        }
      }
    }
    
  3. Restart Claude Desktop (Because It's a New Day)

    1. Close and reopen Claude Desktop to apply the changes.
  4. Verify That It's Working

    1. Once everything is set up, let's test if Claude can actually talk to Playwright now.
    2. Open Claude and ask: "List all available MCP tools."
    3. If playwright-mcp is installed correctly, it should list tools like:
      1. get-context
      2. get-full-dom
      3. get-screenshot
      4. execute-code
      5. init-browser
      6. validate-selectors
    4. Ask Claude to init browser and a browser should open up after your approval!

Now that the Calude has access to the web pages. You can ask it write highly contextual tests! Head to the Claude tutorial or Cursor tutorial to understand it in details.

📖 View Documentation

FAQ

What is the Playwright Recorder MCP server?
Playwright Recorder is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Playwright Recorder?
This profile displays 64 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.8 out of 5—verify behavior in your own environment before production use.

Use Cases

Web Research & Information Gathering

Fetch and extract information from websites automatically

Example

Research competitor pricing, scrape product reviews, monitor news mentions

Automate 5-10 hours/week of manual web research

Content Monitoring & Alerts

Track website changes, new content, price updates

Example

Monitor competitor blog for new posts, track stock availability, watch for pricing changes

Stay informed without manual checking, never miss important updates

Data Extraction & Aggregation

Extract structured data from multiple websites

Example

Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data

Build datasets 100x faster than manual copying

API-less Integration

Interact with services that don't offer APIs

Example

Check form submissions, validate website functionality, test user flows

Automate interactions with any website, even without API

Implementation Guide

Prerequisites

  • Claude Desktop or Cursor with MCP support
  • Understanding of web scraping ethics and robots.txt
  • Rate limiting awareness to avoid overwhelming target sites
  • Knowledge of legal restrictions on data collection

Time Estimate

20-40 minutes including configuration and testing

Installation Steps

  1. 1.Install web automation MCP server via npm or pip
  2. 2.Configure allowed domains and rate limits in MCP config
  3. 3.Test with simple fetch: 'Get content from example.com'
  4. 4.Progress to extraction: 'Extract all product prices from this page'
  5. 5.Set up monitoring: 'Check this URL daily for changes'
  6. 6.Parse structured data: 'Create CSV from this table'
  7. 7.Respect robots.txt and rate limits always

Troubleshooting

  • 403 Forbidden: Website blocks bots—respect their wishes, use official API instead
  • Rate limit errors: Slow down requests, add delays between fetches
  • Stale data: Target site changed HTML structure—update selectors
  • Timeout errors: Site is slow or blocking—increase timeout, try different user agent
  • JavaScript-rendered content: Use headless browser MCP servers for dynamic sites

Best Practices

✓ Do

  • +Check robots.txt and respect crawl rules
  • +Rate limit requests: 1-2 requests/second maximum
  • +Use official APIs when available instead of scraping
  • +Identify your bot with descriptive user agent
  • +Cache results to minimize repeated requests
  • +Handle errors gracefully with retries and fallbacks
  • +Validate extracted data for accuracy

✗ Don't

  • Don't scrape sites that explicitly forbid it (robots.txt, ToS)
  • Don't overwhelm servers with rapid requests—use rate limiting
  • Don't scrape personal data without consent and legal basis
  • Don't ignore copyright on extracted content
  • Don't assume HTML structure is stable—handle changes
  • Don't use scraped data for commercial purposes without permission

💡 Pro Tips

  • Use CSS selectors or XPath for robust data extraction
  • Set up monitoring alerts for extraction failures (structure changed)
  • Implement exponential backoff for retries on failures
  • Store raw HTML for reprocessing if extraction logic changes
  • Combine with data analysis tools for insights from extracted data
  • Consider using official APIs or RSS feeds as more stable alternatives

Technical Details

Architecture

MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.

Protocols

  • HTTP/HTTPS
  • WebSocket (for real-time sites)
  • Puppeteer/Playwright (for JavaScript sites)

Compatibility

  • Static HTML sites
  • JavaScript-rendered SPAs (with headless browser)
  • REST APIs
  • GraphQL endpoints

When to Use This

✓ Use When

Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.

✗ Avoid When

Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.

Integration

  • Scheduled monitoring with change detection
  • Multi-source data aggregation pipelines
  • Fallback to web scraping when API rate limits hit
  • Headless browser for JavaScript-heavy sites

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.864 reviews
  • Dhruvi Jain· Dec 20, 2024

    I recommend Playwright Recorder for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Liam Diallo· Dec 20, 2024

    Playwright Recorder has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Yuki Dixit· Dec 16, 2024

    Playwright Recorder is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Yusuf Mehta· Dec 12, 2024

    Playwright Recorder is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Layla Srinivasan· Dec 8, 2024

    We evaluated Playwright Recorder against two servers with overlapping tools; this profile had the clearer scope statement.

  • Liam Okafor· Dec 4, 2024

    Useful MCP listing: Playwright Recorder is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Layla White· Nov 27, 2024

    Playwright Recorder is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Hiroshi Haddad· Nov 23, 2024

    Playwright Recorder is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Ava Okafor· Nov 15, 2024

    According to our notes, Playwright Recorder benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Oshnikdeep· Nov 11, 2024

    Strong directory entry: Playwright Recorder surfaces stars and publisher context so we could sanity-check maintenance before adopting.

showing 1-10 of 64

1 / 7