Playwright MCP Docker Environment

Created By
iuilla year ago
This project provides a Docker Compose environment to run the '@playwright/mcp' server.
Overview

What is Playwright MCP Docker Environment?

Playwright MCP Docker Environment is a project that provides a Docker Compose setup to run the '@playwright/mcp' server, facilitating easy management and deployment of the Playwright MCP server for various clients.

How to use Playwright MCP Docker Environment?

To use this project, clone the repository, create and configure a .env file, and then build and start the Docker container using Docker Compose commands.

Key features of Playwright MCP Docker Environment?

  • Easy setup with Docker Compose for the Playwright MCP server.
  • Configuration options for headless and headed modes.
  • Support for various client configurations like VSCode and Cline.

Use cases of Playwright MCP Docker Environment?

  1. Running automated tests in a headless browser environment.
  2. Integrating with development tools for real-time feedback.
  3. Facilitating browser automation tasks in a controlled environment.

FAQ from Playwright MCP Docker Environment?

  • What are the prerequisites for using this project?

You need Docker and Docker Compose installed on your machine.

  • How do I switch between headless and headed modes?

You can switch modes by changing the HEADLESS variable in the .env file and restarting the container.

  • Can I use this project on Windows?

Yes, but ensure that your WSL or X Server settings are correctly configured for GUI applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iuill
Star
0
Language
Shell
License
MIT license

Recommend Servers

View All
Voyei

3 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.

14 hours ago