scroll-world
A skill that turn any brand into a scrollable 3D world landing page
Query Playwright test analytics from AI assistants: flaky tests, failures, CI time lost to retries.
Skills that teach the AI this kind of work; they work alongside this one
A skill that turn any brand into a scrollable 3D world landing page
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 17/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 29/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 26 (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Squally. Follow https://mcp.popnx.com/i/squally-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 16, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Squally key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Squally for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "squally": { "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SQUALLY_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Squally tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
SettingsDeveloperEdit Config
{
"mcpServers": {
"squally": {
"command": "npx",
"args": [
"-y",
"squally-mcp"
],
"env": {
"SQUALLY_API_KEY": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Squally and tell me what you can do for me, then show me one thing✓ If Claude says it is using Squally or shows a Squally tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SQUALLY_API_URL Base URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Squally yet
Squally runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Squally
B · Others in Marketing & social media that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Squally key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Squally for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user squally --env SQUALLY_API_KEY=your-value -- npx -y squally-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SQUALLY_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Squally tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user squally --env SQUALLY_API_KEY=your-value -- npx -y squally-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Squally listed as connected
Use Squally and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Squally or shows a Squally tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SQUALLY_API_URL Base URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Squally key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Squally for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "squally": { "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SQUALLY_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Squally tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Squally settings, SQUALLY_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Squally and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Squally or shows a Squally tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SQUALLY_API_URL Base URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Squally key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Squally for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "squally": { "type": "stdio", "command": "npx", "args": [ "-y", "squally-mcp" ], "env": { "SQUALLY_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SQUALLY_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Squally tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Squally settings, SQUALLY_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Squally and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Squally or shows a Squally tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SQUALLY_API_URL Base URL of the Squally API. Defaults to https://app.squally.dev.SQUALLY_USE_SYSTEM_CA Set to 0 to use only Node's bundled certificates instead of also trusting the operating system's certificate store.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
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 secret required envSQUALLY_API_URL envSQUALLY_USE_SYSTEM_CA envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: squally-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified against the domain squally.dev (the registry checks domain ownership)
Code last changed 4 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for squally-mcp@0.10.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/squally-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SQUALLY_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 4 days ago, and the latest version (0.10.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| This one Squally | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | Yes | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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?".
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.
Worth knowing before you hand a key to an assistant. Through this server an agent can read:
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.
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 mcp add squally --scope user \
--env SQUALLY_API_KEY=sqly_ro_your_key_here \ -- npx -y squally-mcp
~/.codex/config.toml:
[mcp_servers.squally]
command = "npx" args = ["-y", "squally-mcp"] env = { SQUALLY_API_KEY = "sqly_ro_your_key_here" }
~/.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_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" } } } }
| 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.
npx downloads the package, which can take longer than Claude Desktop's 60-second start-up limit. Install it once beforehand with npm install -g squally-mcp; npx -y squally-mcp then runs that copy without a download. Update it with the same command.%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.claude_desktop_config.json.| 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.
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).
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.
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:
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.
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 } ] } ] }
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.
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