原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

k11 Playwright QA

作者:K11-Software-Solutions版本 0.3.0i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.K11-Software-Solutions/playwright-qa

安装方法

What it does

User stories to verified Playwright tests, and self-healing locators with an audit trail.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 网页与浏览器

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

作者:google-research★ 35,6291 个 skill

Skill · 操作手册

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

作者:BigBodyCobain★ 11,6021 个 skill

Skill · 操作手册

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

作者:gosom★ 8,2091 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 k11 Playwright QA。按照 https://mcp.popnx.com/i/k11-software-solutions-playwright-qa.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月17日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

让 AI 帮你安装

把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Claude 安装 MCP server k11 Playwright QA,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "playwright-qa": { "command": "npx", "args": [ "-y", "k11-playwright-qa-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Playwright QA 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 打开电脑版 Claude 应用的设置文件

    SettingsDeveloperEdit Config

  3. 粘贴这些设置并保存文件

    {
      "mcpServers": {
        "playwright-qa": {
          "command": "npx",
          "args": [
            "-y",
            "k11-playwright-qa-mcp"
          ]
        }
      }
    }
  4. 退出 Claude 再重新打开

  5. 试一试

    用 k11 Playwright QA 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 k11 Playwright QA,或回答中出现 k11 Playwright QA 的工具名称,就表示连接成功

1 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • QA_MCP_ROOT 被测项目所在的文件夹(默认为当前目录)
    查看英文原文Folder of the project under test (defaults to the current directory)

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 k11 Playwright QA

k11 Playwright QA 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 k11 Playwright QA 的应用

  • 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
  • 需要先在电脑上安装 Node.js(只需一次)
  • 需要先在电脑上安装 Node.js(只需一次)
  • 需要先在电脑上安装 Node.js(只需一次)

B · 网页与浏览器 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Claude Code 安装 MCP server k11 Playwright QA,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user playwright-qa -- npx -y k11-playwright-qa-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Playwright QA 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --scope user playwright-qa -- npx -y k11-playwright-qa-mcp
  4. 在 Claude Code 中输入 /mcp

    应能看到 k11 Playwright QA 在列表中并显示已连接

  5. 试一试

    用 k11 Playwright QA 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 k11 Playwright QA,或回答中出现 k11 Playwright QA 的工具名称,就表示连接成功

1 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • QA_MCP_ROOT 被测项目所在的文件夹(默认为当前目录)
    查看英文原文Folder of the project under test (defaults to the current directory)

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Cursor 安装 MCP server k11 Playwright QA,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "playwright-qa": { "command": "npx", "args": [ "-y", "k11-playwright-qa-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Playwright QA 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 在 Cursor 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 k11 Playwright QA 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 k11 Playwright QA,或回答中出现 k11 Playwright QA 的工具名称,就表示连接成功

1 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • QA_MCP_ROOT 被测项目所在的文件夹(默认为当前目录)
    查看英文原文Folder of the project under test (defaults to the current directory)

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code,但需要先准备

需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 VS Code 安装 MCP server k11 Playwright QA,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "playwright-qa": { "type": "stdio", "command": "npx", "args": [ "-y", "k11-playwright-qa-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Playwright QA 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 在 VS Code 中以 Agent 模式打开 AI 聊天

  4. 试一试

    用 k11 Playwright QA 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 k11 Playwright QA,或回答中出现 k11 Playwright QA 的工具名称,就表示连接成功

1 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • QA_MCP_ROOT 被测项目所在的文件夹(默认为当前目录)
    查看英文原文Folder of the project under test (defaults to the current directory)

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 k11 Playwright QA 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

安装在电脑上

Claude Code

claude mcp add --scope user playwright-qa -- npx -y k11-playwright-qa-mcp

Claude Desktop (claude_desktop_config.json)

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

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

需要你填写的值

  • QA_MCP_ROOT env
    被测项目所在的文件夹(默认为当前目录)
    查看英文原文Folder of the project under test (defaults to the current directory)

说明为自动翻译,变量名保持原样;不确定时请查看原文。

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

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.3.0
发布到注册中心i
2026年11月17日
代码最后更新i
2026年11月17日
作者
K11-Software-Solutions
软件包
npm: k11-playwright-qa-mcp
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • ✓ 通过

    仍在维护

    代码最后更新于前天

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

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

  • – 不适用

    使用 OAuth 登录

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

  • … 尚未检查

    工具描述中没有隐藏指令

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

已公开的漏洞(OSV.dev)

尚未检查

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/k11-software-solutions-playwright-qa.svg)](https://mcp.popnx.com/en/servers/k11-software-solutions-playwright-qa)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

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

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

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

常见问题

k11 Playwright QA 安全吗?

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

它需要哪些密钥或代码?

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

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

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

它还在维护吗?

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

哪些应用可以使用它?

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

有什么可以替代它?

同一分类中有:Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

Browser Use

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

作者:browser-use广泛使用↓ 167.3万/周★ 12.1万29天前更新

电脑或云端✓ 服务方 · browser-use.com

Apify MCP Server

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

作者:apify广泛使用★ 1.7万前天更新

在云端运行✓ 服务方 · apify.com

Pomerado

Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use

作者:Pomerado正在增长★ 1798昨天更新

在云端运行✓ 服务方 · pomerado.ai

Actionbook

Let your AI agent operate any website through a real, logged-in browser session.

作者:actionbook正在增长★ 163131天前更新

在云端运行✓ 服务方 · actionbook.app
与相似项目对比
本项
k11 Playwright QA
Browser Usechangedetection.io (official)Apify MCP ServerPomeradoActionbook
运行位置需要安装在电脑上云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否是否是否否
可在 Claude 中按 + 添加否是否否否否
基础检查3/35/53/34/44/44/4
许可证MITMITApache-2.0MITMITApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

k11 Playwright QA — MCP server & Claude Code plugin

Turn user stories into Playwright tests that actually pass, and fix the ones a redesign just broke.

AI coding assistants write Playwright tests quickly, but they guess selectors. The tests look right, then fail on the first run, or break the next time someone renames a CSS class. This MCP server gives the assistant the facts it can't guess:

  • Verified locators. It opens the real page and returns locators that match exactly one element, most stable first (getByTestId, getByRole, getByLabel, ...).
  • Story → spec. It turns "As a… I want… so that…", Gherkin scenarios or acceptance-criteria bullets into a Playwright Test skeleton: one test per scenario, one test.step per step.
  • Structured test runs. It runs Playwright and returns per-test results, including the exact locator a failing test was waiting for.
  • Self-healing locators. When the UI changes, it finds the element the test meant and suggests a verified replacement with a confidence score and the reasons. It never silently edits your tests.

Works with Claude Code (as a plugin with /story-to-test and /heal-tests commands), Claude Desktop, and any other MCP client. Listed in the official MCP Registry as io.github.K11-Software-Solutions/playwright-qa.


See it heal

The demo app ships in two versions. In v2 a redesign renamed every id, changed the button text from "Sign in" to "Log in", swapped the CSS classes and added a "Continue with Google" button. A test using page.locator('#login-btn') fails. heal_locator returns (trimmed):

{

"status": "healed", "original": "page.locator('#login-btn')", "suggestion": "page.getByRole('button', { name: 'Log in' })", "confidence": 0.87, "reasons": [ "name equivalent: \"Sign in\" → \"Log in\"", "id similar (50%): \"login-btn\" → \"signin-submit\"", "role matches", "type matches", "tag matches", "classes similar (64%): \"btn btn-primary\" → \"cta cta-primary\"" ], "candidates": [ { "locator": "page.getByRole('button', { name: 'Log in' })", "score": 0.87 }, { "locator": "page.getByRole('button', { name: 'Continue with Google' })", "score": 0.42 }, { "locator": "page.getByRole('heading', { name: 'Log in to Acme Store' })", "score": 0.15 } ], "referenceSource": "baseline" }

It picked the right button over the look-alike, and the suggestion is a role-based locator that would have survived the redesign in the first place.

Tools

ToolWhat it does
explore_pageOpens a URL and lists elements with locators verified to match exactly one element.
check_locatorCounts what a locator matches on a page (1 = good) and whether it's visible.
parse_user_storyUser story → structured scenarios + a Playwright Test skeleton.
write_testWrites a spec into tests/. Refuses paths outside it; won't overwrite unless asked.
run_testsRuns Playwright Test and returns per-test results with the failing locator.
capture_baselineWhile tests pass, fingerprints the element each locator matches (.qa-mcp/baselines.json).
heal_locatorFinds the intended element after a UI change and suggests a verified replacement.
save_login_stateLogs in once with a few steps and saves the session for the other tools and your tests.
list_devicesPhone and tablet profiles for mobile web testing (iPhone, Pixel, Galaxy, iPad…).

explore_page, check_locator, capture_baseline and heal_locator accept an optional session to reach pages behind a login or several steps into a flow, and an optional device (e.g. "iPhone 15") for mobile web. run_tests accepts a Playwright project (e.g. "Mobile Safari").

Prompt: `story_to_playwright`, a guided workflow from story to passing test.

How self-healing works

  1. Baseline. While tests pass, capture_baseline records each element's fingerprint: role, accessible name, test id, id, name, type, label, placeholder, classes, text and href.
  2. Detect. When run_tests reports a failure, it includes the locator Playwright was waiting for.
  3. Match. heal_locator scores every visible element on the current page against the fingerprint. It uses exact matching for stable attributes and fuzzy, synonym-aware matching for text and ids ("Sign in" ≈ "Log in", btn ≈ button).
  4. Verify. The best match gets the most stable locator that matches exactly one element on the live page.
  5. Decide. It reports healed only when the confidence is at least 0.55 and clearly ahead of the runner-up. Otherwise it reports needs_review with the top candidates, or not_found if nothing resembles the original. Without a baseline it falls back to what the locator itself implies and says so.

Commit .qa-mcp/baselines.json to your repository so healing works in CI. Do not commit .qa-mcp/auth/, which holds login sessions; save_login_state adds it to .gitignore for you.

Pages behind a login and multi-step flows

Every page tool accepts a session:

{

"url": "https://shop.example.com/login", "session": { "storage_state": ".qa-mcp/auth/default.json", "steps": [ { "action": "click", "locator": "page.getByRole('link', { name: 'My orders' })" }, { "action": "wait_for", "locator": "page.getByRole('heading', { name: 'Order history' })" } ] } }

  • `storage_state` is a saved login. Create one with save_login_state (log in once with steps) or reuse the file from your Playwright global setup. It must be inside the project.
  • `steps` run after the start page loads: goto, click, fill, press, select, check, uncheck and wait_for, up to 25. Locators are parsed the same safe way as everywhere else.
  • Secrets stay out of prompts and logs. Write "value": "${ENV:APP_PASSWORD}" and the value is read from the environment. Results show the placeholder, and literal fill values are masked as •••.
  • Baselines are stored under the page the steps end on, so capturing and healing with the same session line up.

Mobile web

Most sites show phones a different layout: a hamburger menu instead of a nav bar, hidden columns, separate buttons. Locators that work on desktop often don't on mobile, and the other way round. Every page tool takes a device (any of Playwright's built-in profiles: screen size, pixel density, touch and mobile user agent):

explore_page   { url, device: "iPhone 15" }           → the elements a phone user actually sees

check_locator { url, locator, devices: ["desktop", "iPhone 15", "Pixel 7"] } → "unique and visible on every device", or which device it fails on capture_baseline / heal_locator { ..., device: "Pixel 7" } → baselines are kept per device heal_locator { ..., check_devices: ["desktop"] } → warns if a mobile fix isn't valid on desktop

heal-ci across Playwright projects. If your playwright.config has desktop and mobile projects, each failure is healed on the device its project emulates. Projects named after a device ("Pixel 7") or Playwright's template names ("Mobile Chrome", "Mobile Safari") are recognised; map any others in heal.config.json ("projects": { "Phones": "iPhone 15" }). When one broken locator fails on several devices:

  • the devices must agree on the replacement. If each finds a different "best" element (say separate desktop and mobile buttons with their own test ids), heal-ci looks for a locator that is unique on all of them, such as the shared role and name, and otherwise asks a person;
  • a change is kept only if the test then passes in every project, so a fix for mobile can never silently break desktop.

Pages are emulated in Chromium, which is right for responsive layouts and locators. For Safari-specific rendering, keep a WebKit project in your Playwright config. Native mobile apps need Appium, not Playwright.

Healing in CI, with an audit trail

heal-ci repairs locators broken by a UI change and opens a pull request that explains every change:

npx -y k11-playwright-qa-mcp heal-ci --apply
  1. Runs your Playwright suite.
  2. For each locator failure, works out the page the test was on (from .qa-mcp/heal.config.json, or the test's own page.goto(...)) and heals against the committed baseline on the device the test's Playwright project emulates, logging in first if the config says so.
  3. Applies a change only when confidence is at least 0.7 (--min-confidence) and clearly ahead of the runner-up.
  4. Re-runs the healed tests and reverts any change whose test still fails in any Playwright project. Each change is kept or reverted on its own merits.
  5. Leaves failures that aren't about locators alone: they may be real bugs.
  6. Writes heal-report.md (the pull-request description) and heal-report.json (full evidence).

Without --apply, it's a dry run that only reports suggestions. A real report from the demo app's redesign:

1 healed and verified, 0 suggested, 1 reverted, 1 needs review, 0 not found, 1 failure not caused by locators.

| Test | Old locator | New locator | Confidence | Runner-up | Re-run |

|---|---|---|---|---|---|

| Account › shows my orders | page.locator('#view-orders') | page.getByRole('button', { name: 'View orders' }) | 82% | View returns button (59%) | passed |

Needs a person: "Edit profile" link → best candidate "Account settings" (45%), not confident enough to change. "Open cart" healed at 85%, but the test still failed because the cart message changed too, so the change was reverted.

Not caused by locators: "has the account title" (the page title changed). Untouched.

Copy docs/heal-locators.yml into your app's .github/workflows/ to run it on a schedule and open the pull request automatically, and docs/heal.config.example.json to .qa-mcp/heal.config.json to tell it how to log in.

How it compares to Microsoft's Playwright MCP

Playwright MCP lets an AI drive a browser through any task, and Playwright's test agents (planner, generator, healer) build on it. Use them to explore and automate broadly. Use k11 Playwright QA when you need test maintenance you can audit:

Playwright MCP and test agentsk11 Playwright QA
Healing evidenceThe agent's reasoningConfidence score, specific reasons and the runner-up, in a report
Reference pointThe current pageA fingerprint saved when the test last passed
Same input, same resultVaries by run and modelYes
Edits to your testsThe agent edits themOnly verified, confident changes; the rest goes to a person
CI outputAgent sessionA pull request with an audit report

They work well together: drive flows with Playwright MCP, and keep your suite healthy with k11 Playwright QA.

Install

Requires Node 20+.

First, once per machine, install the Chromium build the server uses:

npx -y k11-playwright-qa-mcp install-browsers
Claude Code: plugin (recommended)

Adds the MCP tools plus the /story-to-test and /heal-tests commands:

/plugin marketplace add K11-Software-Solutions/k11techlab-playwright-qa-mcp

/plugin install playwright-qa@k11-qa-tools

Claude Code: MCP server only

From your app's project folder:

claude mcp add playwright-qa -- npx -y k11-playwright-qa-mcp
Claude Desktop and other MCP clients
{

"mcpServers": { "playwright-qa": { "command": "npx", "args": ["-y", "k11-playwright-qa-mcp"], "env": { "QA_MCP_ROOT": "/path/to/your/app" } } } }

From source
git clone https://github.com/K11-Software-Solutions/k11techlab-playwright-qa-mcp

cd k11techlab-playwright-qa-mcp npm install && npx playwright insta

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