Deno 2 Playwright Model Context Protocol Server Example

Created By
jakedahna year ago
A Model Context Protocol server that provides browser automation capabilities using Playwright and Deno 2.
Overview

what is Deno 2 Playwright MCP Server?

Deno 2 Playwright MCP Server is a Model Context Protocol server that provides browser automation capabilities, allowing LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment using Playwright and Deno 2.

how to use Deno 2 Playwright MCP Server?

To use the Deno 2 Playwright MCP Server, you must build the appropriate binary for your operating system and configure it in your application settings to point to the binary executable.

key features of Deno 2 Playwright MCP Server?

  • Browser automation capabilities using Playwright
  • Ability to execute JavaScript in a real browser environment
  • Supports various platforms including macOS, Linux, and Windows

use cases of Deno 2 Playwright MCP Server?

  1. Automating web testing for applications
  2. Taking screenshots of web pages programmatically
  3. Capturing and running JavaScript codes in a headless browser

FAQ from Deno 2 Playwright MCP Server?

  • What is the compatibility of Deno 2 Playwright MCP Server?

The server is compatible with Deno 2 and can be built for macOS, Linux, and Windows environments.

  • Is it possible to customize the server settings?

Yes! You can customize the server settings by modifying the configuration file to point to the specific executable binary.

  • How do I build the server for different platforms?

You can build the server using specific deno tasks such as deno task build-mac, deno task build-linux-x86_64, etc.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jakedahn
Star
-
Language
-
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago