deno2-playwright

This MCP server provides browser automation capabilities via Playwright using a Deno 2-based server binary. It enables an LLM to interact with real web pages, capture screenshots, evaluate and run JavaScript in the page context, and perform typical browser automation tasks through the MCP interface. To use it, configure your MCP client (for example Claude’s integration) to point at the published binary path so the MCP client can forward model requests to the server. Once running, you can request actions like navigating to a URL, selecting elements, taking screenshots, extracting page content, and executing scripts within a live browser instance. The server is designed to run as a standalone binary, which helps avoid runtime dependencies beyond the Deno-compiled executable.

Prerequisites:

• A host machine with a supported OS (macOS, Linux, or Windows) and a compatible CPU architecture for the prebuilt binary.
• Deno installed if you plan to build from source (optional if using prebuilt binaries).

Installation steps:

1. Clone the repository or download the prebuilt binary for your platform.

2. If building from source, install Deno and run the provided build tasks:

   • deno task build-mac
   • deno task build-linux-x86_64
   • deno task build-linux-ARM64
   • deno task build-windows-x86_64

3. Ensure the resulting playwright-server binary is executable.

4. Update your MCP client configuration to point to the binary path, as shown in the example configuration:

   { "mcpServers": { "playwright": { "command": "/path/to/deno2-playwright-mcp-server/playwright-server" } } }

5. Run the server by invoking the configured command via your MCP client or directly from the command line if you prefer to test locally.

Notes:

• The server is designed to run as a standalone binary, minimizing runtime dependencies.
• If you encounter permission or path issues, ensure the binary has execute permissions and that the path is correct.

Common considerations:

• Platform-specific binaries: use the build task corresponding to your OS/architecture (macOS, Linux x86_64, Linux ARM64, Windows x86_64).
• After starting, verify that the MCP client can reach the server and that requests (e.g., navigate, screenshot, and script execution) respond in a timely manner.
• For debugging, run the binary directly from the terminal to inspect startup logs and potential error messages.
• If you modify the config, ensure the JSON structure remains valid and the server name matches your MCP client’s expectations (e.g., "playwright").
• Security: restrict access to the binary and the host environment where the browser automation occurs to prevent unauthorized page interactions.