Playwright MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| playwright_navigateC | Navigate to a URL |
| playwright_screenshotC | Take a screenshot of the current page or a specific element |
| playwright_clickC | Click an element on the page |
| playwright_fillC | fill out an input field |
| playwright_selectC | Select an element on the page with Select tag |
| playwright_hoverC | Hover an element on the page |
| playwright_evaluateC | Execute JavaScript in the browser console |
| playwright_getC | Perform an HTTP GET request |
| playwright_postC | Perform an HTTP POST request |
| playwright_putC | Perform an HTTP PUT request |
| playwright_patchC | Perform an HTTP PATCH request |
| playwright_deleteC | Perform an HTTP DELETE request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools cleanly separate into three categories: HTTP methods (GET, POST, PUT, PATCH, DELETE), browser interaction (click, fill, hover, navigate, screenshot, select), and JavaScript execution (evaluate). There is no overlap between these functional areas.
All tools follow a perfect 'playwright_verb' naming pattern with consistent snake_case throughout. The verb choices are precise and descriptive (click, fill, hover, navigate, evaluate, screenshot, select, get, post, put, patch, delete), creating a highly predictable and readable naming convention.
12 tools is well-scoped for a Playwright automation server. The count provides comprehensive coverage of core browser automation and HTTP testing capabilities without being overwhelming. Each tool clearly earns its place in the toolkit.
The tool surface is nearly complete for browser automation and HTTP testing. It covers navigation, interaction, JavaScript execution, screenshots, and full HTTP method support. Minor gaps might include waiting/retry mechanisms or file upload/download operations, but core workflows are well covered.