Playwright_mcp_programmatic

Created By
hydroweavera year ago
Testing Programmatic Access for Playwright MCP Server
Overview

what is Playwright MCP Programmatic?

Playwright MCP Programmatic is a tool designed for testing programmatic access to the Playwright MCP server, enabling developers to automate browser interactions and testing workflows.

how to use Playwright MCP Programmatic?

To use Playwright MCP Programmatic, navigate to the project directory and run the following commands:

  1. cd \playwright_mcp_programmatic\dist
  2. npx tsc
  3. node index.js

key features of Playwright MCP Programmatic?

  • Programmatic access to Playwright MCP server for automated testing.
  • Supports TypeScript for enhanced development experience.
  • Easy setup and execution of tests through command line.

use cases of Playwright MCP Programmatic?

  1. Automating end-to-end testing of web applications.
  2. Validating API responses through browser interactions.
  3. Integrating with CI/CD pipelines for continuous testing.

FAQ from Playwright MCP Programmatic?

  • What programming language is used?

The project is developed using TypeScript.

  • Is there any setup required before running the tests?

Yes, you need to compile the TypeScript files using npx tsc before executing the tests.

  • Can I contribute to the project?

Yes, contributions are welcome! Please check the repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hydroweaver
Star
0
Language
TypeScript
License
-

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 hours ago
Gpt Scrambler

2 days ago