Skip to main content
Glama
jsdf

playwright-slim-mcp

by jsdf

Related Servers

Alternatives to playwright-slim-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      A lightweight local MCP server that runs axe-core accessibility audits via Playwright and returns compressed, actionable results optimized for Claude's context window.
      5
      18 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      8
      3,369 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An 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 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An 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 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for lightweight browser automation using Lightpanda with Chrome fallback, providing LLM-optimized accessibility tree snapshots for precise element targeting.
      2
      MIT

    TDQS

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues