Playwright MCP Server

Created By
san0808a year ago
This server provides a comprehensive set of tools to control a web browser instance using Playwright, exposed via the Model Context Protocol (MCP). It allows AI models or other MCP clients to perform complex web browsing tasks across multiple pages/tabs.
Overview

What is Playwright MCP Server?

Playwright MCP Server is a tool that allows users to control web browser instances using Playwright, facilitating complex web browsing tasks through the Model Context Protocol (MCP).

How to use Playwright MCP Server?

To use the server, install the necessary dependencies and Playwright browsers, then run the server using the command python main.py. You can also run it with Server-Sent Events (SSE) on a specified port.

Key features of Playwright MCP Server?

  • Multi-Page Management: Open, close, and switch between multiple browser pages/tabs.
  • Robust Lifecycle Management: Reliable setup and teardown of Playwright resources.
  • Comprehensive Tools: Includes page management, navigation, content retrieval, interaction, waiting, state information, visuals, and JavaScript evaluation.

Use cases of Playwright MCP Server?

  1. Automating web testing across multiple pages.
  2. Scraping data from websites efficiently.
  3. Performing complex interactions on web applications.

FAQ from Playwright MCP Server?

  • Can I control multiple pages at once?

Yes! The server supports managing multiple pages/tabs simultaneously.

  • Is it safe to use JavaScript evaluation tools?

Use caution as these tools can be dangerous if the server is exposed publicly. It's advisable to disable them if security is a concern.

  • What programming language is used?

The server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
san0808
Star
0
Language
Python
License
MIT license
Tags

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago