Playwright MCP Details
Playwright MCP server. A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables large language models (LLMs) to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. The server is designed to be fast, lightweight, and deterministic, offering LLM-friendly tooling and a rich set of browser automation capabilities via MCP tools. It supports standalone operation, containerized deployments, and integration with a variety of MCP clients (Claude Desktop, VS Code, Copilot, Cursor, Goose, Windsurf, and others).
Use Case
The Playwright MCP server exposes a suite of MCP tools that enable an LLM to perform browser automation tasks programmatically without relying on pixel-based input or screenshots. Users configure the server with a standard JSON config, launch it via npx @playwright/mcp@latest, and then invoke the available tools from their MCP client to interact with web pages. Example: configuring the server in a central config file and starting it with npx, then integrating with clients like VS Code or Claude Desktop. Example configurations from the docs include:
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"]
}
}
}amp mcp add playwright -- npx @playwright/mcp@latestclaude mcp add playwright npx @playwright/mcp@latestcodex mcp add playwright npx "@playwright/mcp@latest"{
"mcpServers": {
"playwright": {
"type": "local",
"command": "npx",
"tools": ["*"] ,
"args": ["@playwright/mcp@latest"]
}
}
}<h1 class="text-2xl font-semibold mt-5 mb-3">For VS Code</h1>
code --add-mcp '{"name":"playwright","command":"npx","args":["@playwright/mcp@latest"]}'{
"mcpServers": {
"playwright": {
"command": "docker",
"args": ["run", "-i", "--rm", "--init", "--pull=always", "mcr.microsoft.com/playwright/mcp"]
}
}
}These examples show how to configure and connect various MCP clients to the Playwright MCP server. Once configured, you can call tools such as browser_click, browser_type, browser_navigate, and many others to interact with pages in a structured, programmable way. The configuration also supports advanced options like --isolated, --storage-state for state persistence, and --config to supply a JSON configuration file for the server.
Available Tools (26)
Examples & Tutorials
Real example usage patterns directly from the docs:
1) Standard config snippet for starting Playwright MCP with the latest release (VS Code style):
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"]
}
}
}2) VS Code install command (integrate with Copilot/VSC):
<h1 class="text-2xl font-semibold mt-5 mb-3">For VS Code</h1>
code --add-mcp '{"name":"playwright","command":"npx","args":["@playwright/mcp@latest"]}'3) AMP CLI setup example:
amp mcp add playwright -- npx @playwright/mcp@latest4) Claude Code CLI usage:
claude mcp add playwright npx @playwright/mcp@latest5) Docker-based standalone server config:
{
"mcpServers": {
"playwright": {
"command": "docker",
"args": ["run", "-i", "--rm", "--init", "--pull=always", "mcr.microsoft.com/playwright/mcp"]
}
}
}6) Example with storage state and isolated mode (from User Profile):
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest", "--isolated", "--storage-state={path/to/storage.json}"]
}
}
}Installation Guide
Step-by-step installation instructions with actual commands from the documentation:
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"]
}
}
}amp mcp add playwright -- npx @playwright/mcp@latestclaude mcp add playwright npx @playwright/mcp@latestcodex mcp add playwright npx "@playwright/mcp@latest"{
"mcpServers": {
"playwright": {
"type": "local",
"command": "npx",
"tools": ["*"] ,
"args": ["@playwright/mcp@latest"]
}
}
}Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to npx @playwright/mcp.Go to Program -> Install -> Edit mcp.json. Use the standard config above.{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"playwright": {
"type": "local",
"command": ["npx", "@playwright/mcp@latest"],
"enabled": true
}
}
}droid mcp add playwright "npx @playwright/mcp@latest"Integration Guides
Frequently Asked Questions
Is this your MCP?
Claim ownership and get verified badge
Sponsored
Notes and limitations from the docs:
Node.js 18 or newer; VS Code, Cursor, Windsurf, Claude Desktop, Goose or any other MCP client
Compare Alternatives
Similar MCP Tools
9 related toolsSequential Thinking MCP Server
Sequential Thinking MCP Server provides a dedicated MCP tool that guides problem-solving through a structured, step-by-step thinking process. It supports dynamic adjustment of the number of thoughts and allows revision and branching within a controlled workflow, making it ideal for complex analysis and solution hypothesis development. This server is designed to register a single tool, sequential_thinking, and is integrated with common MCP deployment methods (NPX, Docker) as well as editor integrations like Claude Desktop and VS Code for quick setup. The documentation provides exact configuration snippets, usage patterns, and building instructions to help you deploy and use the MCP server effectively, including Codex CLI, NPX, and Docker installation examples.
N8N MCP Server
An MCP (Model Context Protocol) server designed to integrate Claude Desktop, Claude Code, Windsurf, and Cursor with n8n workflows. This MCP enables users to build, test, and orchestrate complex workflows by exposing a set of tools that bridge Claude’s capabilities with n8n’s automation platform. The project emphasizes robust trigger handling, multi-tenant readiness, and progressive documentation to help developers understand how tools map to real-world workflow tasks. It also outlines future tooling integration points (such as getNodeEssentials and getNodeInfo) to further enhance node-structure awareness within MCP-powered automations.
Hugging Face MCP Server
Hugging Face Official MCP Server connects your large language models (LLMs) to the Hugging Face Hub and thousands of Gradio AI Applications, enabling seamless MCP (Model Context Protocol) integration across multiple transports. It supports STDIO, SSE (to be deprecated but still commonly deployed), StreamableHTTP, and StreamableHTTPJson, with the Web Application allowing dynamic tool management and status updates. This MCP server is designed to be run locally or in Docker, and it provides integrations with Claude Desktop, Claude Code, Gemini CLI (and its extension), VSCode, and Cursor, making it easy to configure and manage MCP-enabled tools and endpoints. Tools such as hf_doc_search and hf_doc_fetch can be enabled to enhance document discovery, and an optional Authenticate tool can be included to handle OAuth challenges when called.
Shadcn UI MCP Server v4
Shadcn UI v4 MCP Server is an advanced MCP (Model Context Protocol) server designed to give AI assistants comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata. It enables multi-framework support (React, Svelte, Vue, and React Native) with fast, cache-friendly access to component source code, demos, and directory structures, empowering AI-driven development workflows. The project emphasizes production-readiness with Docker Compose, SSE transport for multi-client deployments, and smart caching to optimize GitHub API usage while providing rich metadata and usage patterns for rapid prototyping and learning across frameworks.
Figma MCP server
The Figma MCP server enables design context delivery from Figma files to AI agents and code editors, empowering teams to generate code directly from design selections. It supports both a remote hosted server and a locally hosted desktop server, allowing seamless integration with popular editors through Code Connect and a suite of tools that extract design context, metadata, variables, and more. This guide covers enabling the MCP server, configuring clients (VS Code, Cursor, Claude Code, and others), and using a curated set of MCP tools to fetch structured design data for faster, more accurate code generation. It also explains best practices, prompts, and integration workflows that help teams align generated output with their design systems. The documentation includes concrete JSON examples for configuring servers in editors like VS Code and Cursor, as well as command examples for Claude Code integration and plugin installation.
MarkItDown MCP
MarkItDown-MCP is a lightweight MCP (Model Context Protocol) server provided as the markitdown-mcp package. It exposes a STDIO, Streamable HTTP, and SSE MCP server designed for calling MarkItDown to convert content to Markdown. The package focuses on simplicity and accessibility, enabling you to run the MCP server locally via a simple CLI, or in Docker for containerized workflows, with integration options for Claude Desktop. The core capability is exposed through a single tool, convert_to_markdown(uri), which accepts a URI in http:, https:, file:, or data: schemes to fetch content and convert it to Markdown. This MCP server is easy to install with pip and can be used in various transport modes, including STDIO and HTTP/SSE, making it a flexible choice for automations and integrations.
Chrome MCP Server
Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search. It leverages your existing Chrome environment, including login states and configurations, to allow large language models and chatbots to control the browser natively without needing to launch a separate automation process. The project emphasizes privacy by remaining fully local and offers capabilities such as cross-tab context, streamable HTTP communication, and a built-in vector database for semantic search and content analysis. As an early-stage project, it includes a growing set of tools for browser control, inspection, and automation, with ongoing development to broaden compatibility and features.
MCP server for Appwrite docs
The MCP server for Appwrite docs enables LLMs and code-generation tools to interact with comprehensive Appwrite documentation. It empowers AI assistants to access up-to-date API references, SDK guides, and implementation examples, facilitating intelligent code generation, troubleshooting, and best-practice guidance directly from the official docs. This MCP brings real-time context, semantic search, and seamless integration with popular editors and IDEs to accelerate development workflows around Appwrite's APIs and SDKs.
Appwrite MCP server
Appwrite MCP server is a Model Context Protocol server that enables AI models to interact with Appwrite’s backend. It provides a curated set of MCP tools to manage databases, users, functions, teams, and more within your Appwrite project, enabling powerful AI-assisted workflows and natural-language interactions with your backend. The server ships with the Databases tools enabled by default to keep prompts within context limits and can be extended by enabling additional APIs via command-line flags. This makes it easier to build AI-powered applications that leverage Appwrite APIs securely and efficiently.