What it does
Query Playwright test analytics from AI assistants: flaky tests, failures, CI time lost to retries.
- Connects 在你的电脑上运行
- Account or key Needs SQUALLY_API_KEY
- Category 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 17/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 29/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 26 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Squally。按照 https://mcp.popnx.com/i/squally-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
让 AI 帮你安装
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Squally,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "squally": { "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) SQUALLY_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Squally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 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 -v安装一次,所有需要 Node.js 的工具都能用
打开电脑版 Claude 应用的设置文件
SettingsDeveloperEdit Config
粘贴这些设置并保存文件
{ "mcpServers": { "squally": { "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } }只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
退出 Claude 再重新打开
试一试
用 Squally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Squally,或回答中出现 Squally 的工具名称,就表示连接成功
2 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SQUALLY_API_URLBase URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA设置为 0 可仅使用 Node 自带的证书,而不再同时信任操作系统的证书存储。查看英文原文
Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Squally
Squally 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 Squally 的应用
- 需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
- 需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
- 需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
- 需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
B · 营销与社交媒体 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Google Ads + Meta Ads + SEO/GEO MCP✓ ChatGPT
- Cargo✓ ChatGPT
- NotFair✓ ChatGPT
可连接 Claude Code,但需要先准备
需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Squally,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user squally --env SQUALLY_API_KEY=your-value -- npx -y squally-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) SQUALLY_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Squally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 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 -v安装一次,所有需要 Node.js 的工具都能用
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --scope user squally --env SQUALLY_API_KEY=your-value -- npx -y squally-mcp按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude Code 中输入 /mcp
应能看到 Squally 在列表中并显示已连接
试一试
用 Squally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Squally,或回答中出现 Squally 的工具名称,就表示连接成功
2 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SQUALLY_API_URLBase URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA设置为 0 可仅使用 Node 自带的证书,而不再同时信任操作系统的证书存储。查看英文原文
Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Squally,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "squally": { "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) SQUALLY_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Squally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 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 -v安装一次,所有需要 Node.js 的工具都能用
填写你的密钥
在 Squally 的设置中,SQUALLY_API_KEY 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 Squally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Squally,或回答中出现 Squally 的工具名称,就表示连接成功
2 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SQUALLY_API_URLBase URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA设置为 0 可仅使用 Node 自带的证书,而不再同时信任操作系统的证书存储。查看英文原文
Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Squally 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
让 AI 帮你安装
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Squally,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "squally": { "type": "stdio", "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) SQUALLY_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Squally 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
安装 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 -v安装一次,所有需要 Node.js 的工具都能用
填写你的密钥
在 Squally 的设置中,SQUALLY_API_KEY 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 Squally 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Squally,或回答中出现 Squally 的工具名称,就表示连接成功
2 项可选设置(不填也能用)
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
SQUALLY_API_URLBase URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA设置为 0 可仅使用 Node 自带的证书,而不再同时信任操作系统的证书存储。查看英文原文
Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
安装在电脑上
Claude Code
claude mcp add --scope user squally --env SQUALLY_API_KEY=your-value -- npx -y squally-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"squally": {
"command": "npx",
"args": [
"-y",
"squally-mcp"
],
"env": {
"SQUALLY_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"squally": {
"command": "npx",
"args": [
"-y",
"squally-mcp"
],
"env": {
"SQUALLY_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"squally": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"squally-mcp"
],
"env": {
"SQUALLY_API_KEY": "your-value"
}
}
}
}需要你填写的值
SQUALLY_API_KEY机密 必填 envOrganization read key (sqly_ro_...), created in Squally under Organization > Read keys. Not the project ingest key.SQUALLY_API_URLenvBase URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CAenv设置为 0 可仅使用 Node 自带的证书,而不再同时信任操作系统的证书存储。查看英文原文
Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 squally.dev 验证(注册中心会核实域名所有权)
- ✓ 通过
仍在维护
代码最后更新于4天前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
已公开的漏洞(OSV.dev)
OSV.dev 中没有 squally-mcp@0.10.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/squally-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4225 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 4225 个服务器的 89% 更新
- 基础检查结果等于或优于此分类中其他 4225 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Squally 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:SQUALLY_API_KEY
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于4天前,最新版本(0.10.0)于4天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Relaticle
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
ChatbotX
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
X (Twitter) MCP Server by Xquik
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Betterlytics
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| 本项 Squally | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
squally-mcp
A local MCP server that lets a coding agent read your Squally data: which runs happened, how stable each test is, and why a particular test failed.
It runs on your machine over stdio and talks to Squally's read API over HTTPS. Point Claude Code, Codex, Cursor or Claude Desktop at it and ask "why is checkout.spec.ts failing on main?".
Read-only, and structurally so
The server issues HTTP GETs and nothing else. There is no code path that writes, and every tool is annotated readOnlyHint: true, so a client can run them without asking you to confirm each one.
It also cannot reach past your own organization: the key is scoped to one organization, and scoping, plan checks and secret exclusion are all enforced by the API, not by this client.
What an agent can see
Worth knowing before you hand a key to an assistant. Through this server an agent can read:
- your projects and their names;
- your runs, CI and local — commit SHA and message, branch, author, pull request, job key, a link to the CI run, timing, pass/fail counts;
- per-test results for a run, including which shard ran what;
- for a failing attempt: the error message and stack, the code snippet — verbatim source code from your test file — and the full-context prompt (the text Squally's Fix panel copies under Fix in your agent, Without MCP), which carries the same snippet plus an ARIA snapshot of your application at the moment of failure (whatever was on screen, truncated to 3000 characters);
- per-test metrics: how often each test passed on the first try, passed only after a retry, or failed, and how much time retries and failures cost;
- error signatures: failures grouped across runs and branches.
It cannot see screenshots, videos or traces — artifacts are deliberately out of scope — and it cannot see any key, secret or webhook URL.
The key reaches every project in the organization. Create one per machine so a single revocation does not lock out everything, and revoke it under Organization › Read keys when the machine is retired.
Setup
You need an organization read key (sqly_ro_…): Squally → Organization › Read keys → *Create read key*. It is shown once. It is not the same thing as the project ingest key your Playwright reporter uses — this server refuses that one by name.
Requires Node 22 or newer. Read keys are available from the Standard plan.
Claude Code
claude mcp add squally --scope user \
--env SQUALLY_API_KEY=sqly_ro_your_key_here \ -- npx -y squally-mcp
Codex
~/.codex/config.toml:
[mcp_servers.squally]
command = "npx" args = ["-y", "squally-mcp"] env = { SQUALLY_API_KEY = "sqly_ro_your_key_here" }
Cursor
~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": { "squally": { "command": "npx", "args": ["-y", "squally-mcp"], "env": { "SQUALLY_API_KEY": "sqly_ro_your_key_here" } } } }
Claude Desktop
claude_desktop_config.json — macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\ — then restart the app:
{
"mcpServers": { "squally": { "command": "npx", "args": ["-y", "squally-mcp"], "env": { "SQUALLY_API_KEY": "sqly_ro_your_key_here" } } } }
Environment
| Variable | Required | Meaning |
|---|---|---|
SQUALLY_API_KEY | yes | Organization read key, sqly_ro_…. Missing or an ingest key by mistake, and the server exits with one line saying so. |
SQUALLY_API_URL | no | Base URL, default https://app.squally.dev. A trailing / or /api/v1 is tolerated. Useful against a local Squally: http://localhost:3000. |
SQUALLY_USE_SYSTEM_CA | no | 0 keeps Node's bundled certificates only. |
squally-mcp trusts your operating system's certificate store, like your browser does; set SQUALLY_USE_SYSTEM_CA=0 to use Node's bundled certificates only.
Troubleshooting
Claude Desktop
- The server does not start in time. The first start through
npxdownloads the package, which can take longer than Claude Desktop's 60-second start-up limit. Install it once beforehand withnpm install -g squally-mcp;npx -y squally-mcpthen runs that copy without a download. Update it with the same command. - Where the log is. The Microsoft Store build of Claude Desktop writes it to
%LOCALAPPDATA%\Claude\logs\mcp-server-squally.log. Its first lines say which Node runs the server and whether it trusts the system's certificate store; a request that never arrives is logged there with its cause. - Edit the config only while the app is closed. Quit Claude Desktop completely, including from the system tray, before changing
claude_desktop_config.json.
The tools
| Tool | What it answers | Cost |
|---|---|---|
squally-list-projects | Which projects exist. Start here — every other tool needs a projectId from it. | cheap |
squally-find-run | Which runs happened — latest, or by branch, commit SHA, status or source. Counters only. | cheap |
squally-get-run | One run with its per-test rows, across all shards. Which test is red. | cheap |
squally-debug-failure | Every attempt of one test in one run: error, stack, full-context prompt. | cheap |
squally-get-test-metrics | One test's stability, flaky rate and failure rate over a period, across its Playwright projects. | cheap — one test |
squally-list-tests | Every test with a run in the period, once across its Playwright projects, ranked by stability, flaky rate or failures. | cheap — two queries, paged |
squally-list-errors | Error signatures in a period: what keeps failing, grouped, and how its runs ended. | cheap |
For a single test use squally-get-test-metrics, not squally-list-tests — the tool descriptions say so, and the server repeats it in its instructions.
Runs
squally-find-run lists every run, CI and local alike; source (all by default, ci or local) narrows it, and each run says whether it was local. A run's status is the dashboard's word: passed, failed, cancelled, incomplete (a shard timed out, was stopped by the monthly result limit or never reported) or running - and ?status= filters by any of them. A cancelled run is cancelled; cancellation says how, when and by whom. A sharded run is one row, its counters over all its shards with every test once, and the tests a cancel cut off count nowhere.
Each run also says whether it is settled - final and counted; an incomplete run that is not settled still waits for a shard within the run timeout - and, from squally-reporter 0.11.0, which job of its CI run it is (jobKey, from SQUALLY_CI_JOB_KEY; each job is its own run), which attempt, which run it re-ran (rerunOf) and where the CI run is (ciRunUrl; for GitHub Actions also for older reporters when the project has one linked repository).
Playwright projects
A run counts like Playwright: squally-find-run, squally-get-run and squally-debug-failure have one result per test and Playwright project, named with its project (chromium > cart.spec.ts > adds). What is collected across runs — squally-list-tests, squally-get-test-metrics and squally-list-errors — counts a test once across its Playwright projects, by its name without the project (cart.spec.ts > adds), and names the projects in projects: a run failed for the test when it failed in any project, and passed only after a retry when it did so in some project and failed in none. variants carries each project's own numbers. Since 0.9.0 (read API 1.0.0-beta.19); before, each project's variant was its own test.
squally-list-tests takes project as a list (["chromium", "firefox"]) to count only those projects. squally-get-test-metrics takes the name without the project for every project; project, or the stored name with its project, gives one project's variant. squally-debug-failure takes the name squally-get-run lists, project included.
Flaky is a count, not a run status: a run's status is passed, failed, cancelled, incomplete or running, and its counts.flaky says how many tests passed only after a retry.
What the numbers mean
The two test tools count finished runs, CI and local, in the period (7, 14, 30 or 90 days; 30 by default), on every branch unless you name one. A run finishes when all its shards have - or, once the run timeout has passed, with the results its shards reported, like a cancelled run; a shard stopped by the monthly result limit counts like one that timed out. A sharded run counts once, placed in the period by its first shard's start; a run that was a mass failure as a whole is left out. source is all (the default since read API 1.0.0-beta.18; ci before), ci or local - send source=ci for CI runs only - and the response's population names which runs it counted. Per test:
- stability — runs that passed on the first try ÷ runs;
- flakyRate — runs that passed only after a retry ÷ runs;
- failureRate — failed runs ÷ runs.
Each is a fraction from 0 to 1, and null when the test has no run in the period. There is no verdict: nothing calls a test flaky, broken or healthy. The tools return the numbers; the agent — or you — judges them.
Example: squally-list-tests
{ "projectId": "3f7c2a91-5b8e-4d0a-9c61-2e4b7f0d8a15", "perPage": 3 }
The three least stable tests of the last 30 days (abridged):
{
"population": "ci_groups_finished_not_mass_failure", "days": 30, "sort": "stability", "total": 205, "items": [ { "testName": "checkout.spec.ts > Checkout > applies a coupon code", "filePath": "tests/checkout.spec.ts", "projects": ["chromium", "firefox"], "runs": 8, "stability": 0.5, "flakyRate": 0.5, "failureRate": 0, "timeLostMs": 7361, "medianDurationMs": 1840, "topBranch": { "branch": "main", "kind": "retries", "count": 3 }, "variants": [ { "testName": "chromium > checkout.spec.ts > Checkout > applies a coupon code", "project": "chromium", "runs": 8, "flakyRuns": 4 }, { "testName": "firefox > checkout.spec.ts > Checkout > applies a coupon code", "project": "firefox", "runs": 8, "flakyRuns": 0 } ] } ] }
Example: squally-get-test-metrics
{
"projectId": "3f7c2a91-5b8e-4d0a-9c61-2e4b7f0d8a15", "testName": "checkout.spec.ts > Checkout > applies a coupon code" }
The same numbers as that test's row, for one test across its projects (abridged); add "project": "firefox" for firefox's variant alone:
{
"days": 30, "branch": null, "projectFilter": null, "projects": ["chromium", "firefox"], "runs": 8, "stableRuns": 4, "flakyRuns": 4, "failedRuns": 0, "stability": 0.5, "flakyRate": 0.5, "failureRate": 0, "branches": ["feature/saved-carts", "main"] }
Pass the name exactly as Squally shows it — without the project for the test across projects, with it for one project. When it exists in several spec files, the tool answers with the filePath values to retry with; a test with results but no counted run in the period answers runs: 0 and null rates — an answer, not an error.
Development
npm install
npm run build # tsc, then copy the vendored OpenAPI document into dist/ npm test # builds, then runs the suite npm run vendor:openapi # re-fetch the API document; review the diff, then re-pin
The tool schemas are derived from Squally's published OpenAPI document, vendored at src/openapi/v1.json — an input schema is the operation's parameters, an output schema is its 200 response. Nothing is transcribed by hand, so the two cannot drift. test/drift.test.js compares the vendored copy against the live document