Playwright MCP Server vs Pixelcheck
A side-by-side look at the Playwright MCP Server and Pixelcheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Playwright MCP Server for browser automation work as a local process; choose Pixelcheck for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Playwright MCP Server when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
start_codegen_session, end_codegen_session, get_codegen_session.
Choose Pixelcheck when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ANTHROPIC_API_KEY. - You want tools like
audit_url, explore_url, see.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 68/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | ANTHROPIC_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,671 | 6 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 33 | 12 |
| Full listing | View Playwright MCP Server | View Pixelcheck |
Tools & capabilities
Playwright MCP Server tools 33
start_codegen_sessionStart a new code generation session to record Playwright actionsend_codegen_sessionEnd a code generation session and generate the test fileget_codegen_sessionGet information about a code generation sessionclear_codegen_sessionClear a code generation session without generating a testplaywright_navigateNavigate to a URLplaywright_screenshotTake a screenshot of the current page or a specific elementplaywright_clickClick an element on the pageplaywright_iframe_clickClick an element in an iframe on the pageplaywright_iframe_fillFill an element in an iframe on the pageplaywright_fillfill out an input fieldplaywright_selectSelect an element on the page with Select tagplaywright_hoverHover an element on the page- +21 more on the listing page
Pixelcheck tools 12
audit_urlYou want the full audit pipeline against one URL — agent loop, scoring, JSON + HTML report.explore_urlYou want a quick autonomous run with a free-form goal; no scenario YAML needed.seeYou want to look at a URL once and get back DOM summary + screenshot + console errors + an optional natural-language note. 0 LLM cost when `goal` is omitted.actYou want to drive an action sequence (click / fill / scroll / screenshot / natural-language `act` / vision `note`) and get back per-step status + final DOM + screenshot.extractYou want a typed payload back from a URL — pricing tiers, feature lists, FAQ entries — shaped exactly the way you asked for. Hand the tool a JSON Schema; get back `data` matching it plus DOM / console / screenshot.judgeYou want a rubric-driven critique of one URL — aesthetic polish, dark-pattern risk, or any custom rubric. Returns per-criterion scores (0..10) + severity-graded findings with on-screen locations. 1 vision call.compareYou want an A/B comparison of two URLs against the same rubric. Default `double_blind` mode judges each side independently then synthesises a comparison (3 vision calls, free of anchoring bias). `fast` mode is 1 call (cheaper, anchored).list_personasDiscover which personas are installed in a project.list_scenariosDiscover which scenarios are installed in a project.list_capabilitiesSelf-describe the server: every shipped tool with kind / cacheability / static cost band / side-effects / dependency declarations, plus the public env-var table and live result-cache state. Pure introspection — call it once on first connect to plan the rest of your session.calibrate_criticRun the critic calibration gate against labeled fixtures (returns pass/fail + agreement metrics).get_last_reportRead the most recent audit's summary JSON from the local history DB.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Playwright MCP Server
{
"mcpServers": {
"executeautomation-playwright-mcp-server": {
"command": "npx",
"args": [
"-y",
"@executeautomation/playwright-mcp-server"
]
}
}
}
Pixelcheck
{
"mcpServers": {
"pixelcheck": {
"command": "npx",
"args": [
"-y",
"pixelcheck"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Playwright MCP Server is categorized under Browser Automation and uses a local stdio subprocess. Pixelcheck belongs to Browser Automation and uses a local stdio subprocess. Pick Playwright MCP Server for browser automation work and Pixelcheck for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Playwright MCP Server is listed as free. Auth: no auth required. Pixelcheck has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add executeautomation-playwright-mcp-server and pixelcheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Playwright MCP Server has a quality signal of 68/100 (Great) with 5 views, 0 installs and 5,671 GitHub stars. Pixelcheck has 57/100 (Good) with 0 views, 0 installs and 6 GitHub stars.
