Playwright MCP Server

Created By
ma-ponya year ago
Playwright MCP Server 一个基于 FastMCP 框架的专业级 Playwright 浏览器自动化 MCP 服务器,为 LLM 应用提供强大的网页交互和数据提取能力。
Overview

What is Playwright MCP Server?

Playwright MCP Server is a professional-grade browser automation server based on the FastMCP framework, providing powerful web interaction and data extraction capabilities for LLM applications.

How to use Playwright MCP Server?

To use the Playwright MCP Server, install it via PyPI, set up the Playwright browsers, and run the server. You can create browser sessions, navigate to URLs, interact with web pages, and extract data programmatically.

Key features of Playwright MCP Server?

  • Complete control over browser automation using Playwright.
  • Multi-engine support for Chromium, Firefox, and WebKit.
  • Independent browser session management with support for concurrent operations.
  • Intelligent resource management and error recovery mechanisms.

Use cases of Playwright MCP Server?

  1. Automating web testing and scraping tasks.
  2. Extracting data from dynamic web applications.
  3. Integrating with LLM applications for enhanced web interaction.

FAQ from Playwright MCP Server?

  • Can Playwright MCP Server automate any website?

Yes! It can automate most websites, provided they are accessible via a browser.

  • Is Playwright MCP Server free to use?

Yes! It is open-source and free to use under the MIT license.

  • What programming language is used?

The server is developed in Python and requires Python 3.10 or higher.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ma-pony
Star
0
Language
Python
License
MIT 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