原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Playwright E2E MCP

作者:xsignon-secure版本 0.15.0i★ –i在你的电脑上运行
注册名称io.github.xsignon-secure/E2E

安装

概览

作者提供的说明(英文原文)

Diagnose and fix Playwright tests (TS, pytest): CI reports, traces, verified fixes, flaky verdicts.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 网页与浏览器

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "e2e": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add e2e -- npx -y playwright-e2e-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "e2e": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "e2e": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 xsignon-secure 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“网页与浏览器”中的其他服务器比较i

  • 星标数多于此分类中其他 875 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 875 个服务器的 90% 更新
  • 基础检查结果等于或优于此分类中其他 875 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Playwright E2E MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.15.0)于4天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Browser Use, Chrome DevTools MCP, MCP Server Browser

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

作者:browser-use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

电脑或云端★ 120,087MIT16天前更新
安装

Chrome DevTools MCP

作者:ChromeDevTools

MCP server for Chrome DevTools

在你的电脑上运行★ 54,821Apache-2.015天前更新
安装

MCP Server Browser

作者:bytedance

MCP server for browser use access

在你的电脑上运行★ 39,550Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

playwright-e2e-mcp

The test doctor for AI agents.

Your Playwright test fails. Your AI finds out why, fixes it, and proves the fix works , or tells you it's a real bug.

⭐ If it saves you a debugging session, a star helps other Playwright users find it.

Quick start · Features · Tools · Tool reference · GitHub Action · Benchmark · Changelog

An MCP server and agent skill that gives Claude, Cursor, VS Code Copilot, Codex, Gemini and any other MCP client a full Playwright toolkit: a test runner, a failure detective and a fixer that checks its own work. Browser MCPs let an AI click around a page. This one lets it keep your test suite green, for TypeScript and Python suites, on your laptop and in CI. Free, MIT, no account.

❌ Without it / ✅ With it

Without it, your agent sees Timeout 5000ms exceeded waiting for getByTestId('checkout'), guesses a new selector, edits the test and hopes. Or it "fixes" the test by deleting the assertion that caught a real bug.

With it, your agent reads the page as it was when the test failed (from the Playwright trace), swaps in a locator proven unique on that page, re-runs the test and keeps the edit only if it passes. When the button is really gone, it says so: that's an app bug, not a test to patch. And a heal guard blocks any "fix" that went green by checking less.

flowchart LR

A["run-test or load-report (CI)"] --> B["get-failure DOM at failure, requests, console"] B --> C{"suggest-fix"} C -->|"locator proven on the page"| D["apply + re-run"] D -->|green| E["✅ fixed and verified"] D -->|still red| F["↩️ edit reverted"] C -->|"element really gone"| G["🐞 reported as an app bug"] D -.-> H["check-test-change blocks fixes that check less"]

⚡ Quick start

Run this in your project root. It adds the server to every MCP client config it finds (Claude Code, Cursor, VS Code, Gemini CLI, Codex), installs the agent skill and leaves your other servers alone:

npx -y playwright-e2e-mcp init      # --client all | cursor,vscode … · --dry-run

npx -y playwright-e2e-mcp doctor # checks Node, Playwright, browsers, client setup and updates

Then restart your client and ask:

Run my Playwright tests and fix whatever fails.

Or let your agent install it. Paste this into any coding agent:

Install the playwright-e2e-mcp server and skill by following

https://raw.githubusercontent.com/xsignon-secure/E2E/main/llms-install.md

Or add the standard config by hand (works in most clients):

{

"mcpServers": { "playwright-e2e": { "command": "npx", "args": ["-y", "playwright-e2e-mcp"] } } }

Needs: Node.js 22+, and a project with @playwright/test and a browser (npx playwright install chromium) or with pytest-playwright. The server uses its working directory as the project root; if your client starts it elsewhere, add "env": { "PW_MCP_PROJECT_ROOT": "/path/to/your/project" }.

Claude Code

Server and skill, as a plugin:

/plugin marketplace add xsignon-secure/E2E

/plugin install playwright-e2e-mcp@xsignon-secure

Or the server only:

claude mcp add playwright-e2e -- npx -y playwright-e2e-mcp

Claude Desktop

Download the .mcpb extension from the latest release and double-click it. It ships its own dependencies, so no Node setup is needed. On install it asks for your project root: choose the project folder, not your home directory.

You can also add the standard config to claude_desktop_config.json.

Cursor

Click Install in Cursor, or go to Settings → MCP → Add new MCP server and paste the standard config. For one project only, put it in .cursor/mcp.json.

Only fixing failing tests? Install the core tools only: the seven-tool fix loop (--tools=core), about 2.3k tokens of tool definitions instead of 12.1k.

VS Code / GitHub Copilot

Click the Install in VS Code button above, or run:

code --add-mcp '{"name":"playwright-e2e","command":"npx","args":["-y","playwright-e2e-mcp"]}'

Codex

codex mcp add playwright-e2e -- npx -y playwright-e2e-mcp

A Playwright run with retries can take longer than Codex's default 60 s tool timeout. Raise the timeouts in ~/.codex/config.toml:

[mcp_servers.playwright-e2e]

command = "npx" args = ["-y", "playwright-e2e-mcp"] startup_timeout_sec = 60 tool_timeout_sec = 600

Gemini CLI / Qwen Code

Server and skill, as an extension:

gemini extensions install https://github.com/xsignon-secure/E2E

Or paste the standard config into .gemini/settings.json (Qwen Code: .qwen/settings.json).

Windsurf, Cline, Zed, Freebuff and other clients

Add the standard config to the client's MCP config file (Cline: *MCP Servers → Configure*). Clients that take a command, such as Zed, run npx with the arguments -y playwright-e2e-mcp.

Freebuff / Codebuff: drop an mcp.json with the standard config into your project's .agents/ folder. This repo ships one in .agents/mcp.json; Freebuff asks you to trust a repository's .agents/ on first run.

ChatGPT, claude.ai and other remote-only clients

Some clients only accept a remote HTTPS server. This repo ships a Streamable HTTP bridge you can host for free on Vercel, with OAuth sign-in for claude.ai connectors (dynamic registration and Client ID Metadata Documents). See Hosted endpoint. On Vercel the page tools (inspect a page, check selectors, accessibility and Web Vitals audits) run on a bundled Chromium against public URLs. Running and fixing your own tests needs your project, so use the local install for that.

Other ways to install: skill only, Docker, registry, tarball

RouteHow
Skill only, any agentnpx skills add xsignon-secure/E2E
MCP Registryio.github.xsignon-secure/E2E (listing); registry-aware clients find it there
Dockerdocker run -i --rm -v "$PWD:/work" ghcr.io/xsignon-secure/playwright-e2e-mcp (published on each release; see Development)
Straight from GitHub, no npmnpx -y github:xsignon-secure/E2E#v0.15.0 (pin a release tag)
Release tarballnpm install -D https://github.com/xsignon-secure/E2E/releases/download/v0.15.0/playwright-e2e-mcp-0.15.0.tgz
Local checkout"command": "node", "args": ["/path/to/E2E/dist/index.js"]

Updating

Installed withTo update
npx -y playwright-e2e-mcp (the setup above, and what init writes)Restart your MCP client. npx (npm 10, which comes with Node 22) asks npm for the latest version on each launch and fetches it.
npm install -D playwright-e2e-mcp in the projectnpm install -D playwright-e2e-mcp@latest
npm install -g playwright-e2e-mcpnpm install -g playwright-e2e-mcp@latest
GitHub Action uses: xsignon-secure/E2E@v0.x.yChange the tag (Dependabot's github-actions updates do it for you)
Dockerdocker pull ghcr.io/xsignon-secure/playwright-e2e-mcp:latest
Claude Desktop bundle (.mcpb)Download the new bundle from the latest release and open it
Git clonegit pull && npm ci
Agent skill copied by init or npx skills addRun the same command again

npx -y playwright-e2e-mcp doctor tells you whether a newer version is out and prints the command for your setup. Upgrade notes for each release are on the releases page.

💬 What you can ask

You ask your AI…It does this
🏃"Run my tests"Runs the suite and reports every failure with file, line, cause and a fix hint. One root cause breaking 30 tests shows up as one problem.
🔍"Why did this fail?"Reads Playwright's trace: the page at the moment of failure, the broken request, the console error. No guessing.
🛠️"Fix it"Swaps in a locator proven unique on that page, re-runs the test and undoes the edit if it's still red. If the element is really gone, it tells you it's an app bug.
☁️"Why did CI fail?"Loads the CI job's report (sharded blob reports too) and its traces, so the same diagnosis and fixes work on CI failures.
🎲"Is this test flaky?"Re-runs it with retries off, alone and in shuffled order, and names the race, the shared state or the test it depends on, with the seed that reproduces it.
🎯"Which commit broke this?"Bisects git history in a throwaway worktree and names the first bad commit, its diff and the failure there.

| 📈 | "What's been breaking lately?" | Ranks flaky, newly broken and slow tests from the run history and names the commit where

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx