TESIGN
SAVED

EN · KO

Auto-generated — not yet edited · only the numbers are verified

  1. TESIGN / RADAR
  2. REPOSITORY CARD
  3. microsoft/playwright-mcp

microsoft/playwright-mcp

Playwright MCP server

★ 37.1k▲ +4 / 7dDaily star increases over 14 days. Hollow bars mean no data. The last day may be partial.2026-09-03 no data2026-09-04 no data2026-09-05 +62026-09-06 +42026-09-07 no data2026-09-08 no data2026-09-09 no data2026-09-10 no data2026-09-11 +22026-09-12 no data2026-09-13 no data2026-09-14 no data2026-09-15 no data2026-09-16 +2largest one-day increase in the 14 days+6last 14 days · stars per dayhollow = no data

RANKS All-time #186

AT A GLANCE

LANGUAGE
TypeScript
LICENSE
Apache-2.0
USAGE
Commercial use, redistribution OK. Keep notices; mark changes.
ACTIVITY
last commit 5 days ago ()
TOPICS
  • mcp
  • playwright
HOMEPAGE
https://www.npmjs.com/package/@playwright/mcp
REPOSITORY
GitHub ↗
CATEGORY
AI

A summary, not legal advice.

README EXCERPT

Playwright MCP A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. Playwright MCP vs Playwright CLI This package provides MCP interface into Playwright. If you are using a coding agent , you might benefit from using the CLI+SKILLS instead. - CLI : Modern coding agents increasingly favor CLI–based workflows exposed as SKILLs over MCP because CLI invocations are more token-efficient: they avoid loading large tool schemas and verbose accessibility trees into the model context, allowing agents to act through concise, purpose-built commands. This makes CLI + SKILLs better suited for high-throughput coding agents that must balance browser automation with large codebases, tests, and reasoning within limited context windows. Learn more about Playwright CLI with SKILLS . - MCP : MCP remains relevant for specialized agentic loops that benefit from persistent state, rich introspection, and iterative reasoning over page structure, such as exploratory automation, self-healing tests, or long-…

The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.

TIMELINE

  1. Repository created
  2. Last push
  3. FIRST SEEN BY TESIGN ◌ BACK CATALOG

AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →

If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.