测试

Created By
microsofta year ago
Overview

What is Playwright MCP?

Playwright MCP is a Model Context Protocol server that provides browser automation capabilities using Playwright. It allows large language models (LLMs) to interact with web pages through structured accessibility snapshots, eliminating the need for screenshots or visually-tuned models.

How to use Playwright MCP?

To use Playwright MCP, install the server with your preferred client (e.g., VS Code, Cursor). A typical configuration involves using the command npx @playwright/mcp@latest to set up the server.

Key features of Playwright MCP?

  • Fast and lightweight, utilizing Playwright's accessibility tree instead of pixel-based input.
  • LLM-friendly, operating purely on structured data without the need for vision models.
  • Deterministic tool application, reducing ambiguity compared to screenshot-based methods.

Use cases of Playwright MCP?

  1. Automating web interactions for testing and development.
  2. Enabling LLMs to perform tasks on web pages without visual input.
  3. Facilitating browser automation in environments without a display.

FAQ from Playwright MCP?

  • Can Playwright MCP be used with any browser?

Yes, it supports multiple browsers including Chrome, Firefox, and WebKit.

  • Is Playwright MCP free to use?

Yes, it is open-source and free for everyone.

  • What are the system requirements for Playwright MCP?

You need Node.js 18 or newer to run Playwright MCP.

Server Config

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
microsoft
Star
-
Language
-
License
-

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