Playwright Sse MCP Server

@torohash

Repository

Basic information

About Playwright Sse MCP Server

playwright/mcpをsseで外部から触るためのやつ

#mcp

Playwright Sse MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "playwright-sse-mcp-server": {
      "command": "docker",
      "args": [
        "network",
        "create",
        "mcp-network"
      ]
    }
  }
}

Playwright Sse MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is playwright-sse-mcp-server?

playwright-sse-mcp-server provides Playwright as an MCP (Model Context Protocol) server, enabling MCP clients to use Playwright’s browser automation features. It runs inside a Docker container and is intended for developers who need browser control from MCP-compatible tools.

How to use playwright-sse-mcp-server?

Clone the repository and run docker compose up --build in the project root. The server starts on port 3002 by default; set the PORT environment variable for a custom port. Connect from other containers on the same Docker network via playwright-sse-mcp-server:<PORT>/sse, or from the host via localhost:<PORT>/sse. For Roo Code, configure the MCP settings with the SSE URL. Helper shell scripts (playwright-mcp-start, playwright-mcp-stop, playwright-mcp-logs) are provided for convenient control.

Key features of playwright-sse-mcp-server

Playwright browser automation exposed via MCP SSE transport
Docker‑based deployment with configurable port (default 3002)
Connects from same Docker network, host, or development containers
Shell scripts for start/stop/logs with persistent mode and restart policies
Requires a pre‑existing Docker network named mcp-network

Use cases of playwright-sse-mcp-server

Use an MCP client like Roo Code to automate browser tasks
Run headless Playwright inside a container for testing or scraping
Integrate browser automation into MCP‑based workflows

Frequently asked questions

What are the prerequisites for running the server?

Docker and docker‑compose must be installed. A Docker network named `mcp-network` must exist; if not, create it with `docker network create mcp-network`.

How do I connect from a development container not on `mcp-network`?

Use the host IP or special DNS name. On Docker Desktop (Mac/Windows) use `host.docker.internal:<PORT>/sse`. On Linux, use the host’s IP or the Docker bridge gateway (e.g., `172.17.0.1`). The port must match the one published in `compose.yml`.

Does Cline support this server?

As of 2025/03/27, Cline does not support SSE, so it cannot be used with this server.

Can I change the default port?

Yes, set the environment variable `PORT` before starting the server. For example: `PORT=4000 docker compose up --build`.

What mode does Playwright run in?

The server runs Playwright in headless mode.

Comments

More Browser Automation MCP servers

TinyFish

tinyfish

Give your AI agent the live web. One MCP server for Search, Fetch, Browser, and Agent: browse real sites, extract structured data, fill forms, and run multi-step workflows. Search and Fetch are free.