Skip to main content
Glama
microsoft

Playwright MCP Server

Official
by microsoft

Related Servers

Alternatives to Playwright MCP Server

Related Servers

  • A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually tuned models.
    7
    17,093 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots, providing browser automation capabilities without requiring screenshots or visually-tuned models.
    7
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that provides browser automation capabilities by allowing LLMs to interact with web pages through structured accessibility snapshots. It enables fast, lightweight interaction with web content without the need for vision-tuned models or visual processing.
    Apache 2.0
  • A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without requiring screenshots or vision models.
    22
    6,403,349 npm
    1
    Apache 2.0
  • A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without requiring screenshots or visually-tuned models.
    22
    6,403,349 npm
    Apache 2.0

TDQS

B3.4/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target clear, distinct operations (navigate, click, type, hover, drag, screenshot, snapshot), and the pair browser_network_requests/browser_network_request is explicitly cross-referenced. Some overlap exists between snapshot/find/take_screenshot and between type/fill_form/press_key, but descriptions provide adequate guidance.

Naming Consistency5/5

Every tool follows a strict browser_<action> snake_case convention (browser_navigate, browser_click, browser_take_screenshot, browser_wait_for), making the pattern fully predictable across all 25 tools.

Tool Count3/5

25 tools is at the upper boundary of the ideal range and the surface is broad (tabs, dialogs, media emulation, uploads, network inspection, unsafe code execution). It is defensible for a full browser automation server, but the count feels heavy and encourages selection mistakes.

Completeness5/5

The surface covers navigation, interaction, snapshots, forms, uploads, drag-and-drop, dialogs, console, network, and media emulation with no obvious dead ends for browser automation workflows.

Maintenance

ActivityActive
ResponsivenessResponsive