playwright-slim-mcp
Related Servers
Alternatives to playwright-slim-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA lightweight local MCP server that runs axe-core accessibility audits via Playwright and returns compressed, actionable results optimized for Claude's context window.518 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides browser automation using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots.ISC
- AlicenseAqualityBmaintenanceAn MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.83,369 npm3MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser to navigate, click, type, screenshot, and inspect pages via accessibility snapshots. It also runs multi-step test scenarios with assertions, session recording, visual regression, and console/network monitoring from the terminal.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser, letting it navigate pages, click and type, capture inline screenshots, and read accessibility snapshots. It also runs multi-step JSON test scenarios with assertions, visual regression comparison, and network/console monitoring from the terminal.106 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for lightweight browser automation using Lightpanda with Chrome fallback, providing LLM-optimized accessibility tree snapshots for precise element targeting.2MIT
TDQS
Scored across 25 tools
Most tools have clearly distinct purposes, but browser_snapshot vs browser_snapshot_full, browser_evaluate vs browser_run_code_unsafe, and browser_close vs browser_tabs (closing page vs tab) create some overlap. Descriptions help but an agent must read carefully to pick correctly.
All tools use the browser_ prefix with snake_case and clear verb_noun or noun patterns (e.g., browser_click, browser_navigate, browser_take_screenshot). The convention is consistent throughout with no deviations.
25 tools is at the high end for a single server; while many are necessary for full browser control, some could be consolidated (e.g., snapshot variants, separate network request tools). The count feels heavy and borderline for the 'slim' name.
The surface covers navigation, interaction, forms, keyboard, mouse, tabs, network, console, dialogs, file upload, drag/drop, screenshots, and snapshots. Minor gaps include no explicit forward navigation (only back) or page reload, but these are workaroundable.