Playwright Test Automation

Created By
Prathameshsa year ago
Experiments on using mcp for web automation using playwright / puppeteer map servers
Overview

what is mcp-driven-web-automation?

mcp-driven-web-automation is a project that experiments with using MCP (Multi-Channel Protocol) for web automation, leveraging tools like Playwright and Puppeteer to map servers for automated tasks.

how to use mcp-driven-web-automation?

To use this project, clone the repository from GitHub and follow the setup instructions to configure your environment for web automation tasks using Playwright or Puppeteer.

key features of mcp-driven-web-automation?

  • Integration with Playwright and Puppeteer for web automation.
  • Ability to map servers for efficient task execution.
  • Experimental framework for testing web automation strategies.

use cases of mcp-driven-web-automation?

  1. Automating repetitive web tasks such as form submissions.
  2. Testing web applications across different browsers.
  3. Scraping data from websites for analysis.

FAQ from mcp-driven-web-automation?

  • What is MCP?

MCP stands for Multi-Channel Protocol, which is used for managing multiple communication channels in web automation.

  • Can I use this project for any website?

Yes, as long as the website allows automation and scraping, you can use this project.

  • Is there any documentation available?

Yes, you can find the documentation in the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Prathameshs
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 minutes ago