pw vs io.github.kubeshop/testkube-mcp
pw is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
pw is a plugin bundle for AI coding tools published by Md Faiz Alam. No marketplace we read lists it any more. io.github.kubeshop/testkube-mcp is an MCP server published by kubeshop. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-13. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace afaizalam2003/master-claude-skill | Removed on 2026-10-17 Version: 2.1.2 Forks (GitHub): 2 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.15.2 Forks (GitHub): 179 Stars (GitHub): 1 679 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:43aa88f2d416 Forks (GitHub): 179 Pulls (Docker Hub): 34 731 Stars (Docker Hub): 0 Stars (GitHub): 1 679 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | pwno longer listed · | io.github.kubeshop/testkube-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 2 | 1 679 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 34 731 |
| Forks (GitHub) (differs) | 2 | 179 |
| Last release (differs) | Not published | 2026-11-12 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 28 |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 7, secrets among them: 2 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/afaizalam2003/master-claude-skill | github.com/kubeshop/testkube |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 21 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of pw
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
pw
Production-grade Playwright testing toolkit. 9 skills, 3 agents, 55 templates, plus optional (manually enabled) TestRail/BrowserStack integrations. Generate tests, fix flaky…
-
Playwright Pro turns your AI coding agent into a senior test automation engineer. Instead of generating tutorial-quality tests with brittle CSS selectors, Playwright Pro enforces…
-
Playwright automation toolkit with MCP integration, specialized agent for browser control, and best practice skills
-
playwright
Advanced Playwright skills for end-to-end testing, test architecture, and test automation best practices.
-
Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design…
-
Agent Skill for general-purpose browser automation with Playwright. The agent writes and executes custom scripts for testing pages, validating UX, and automating browser tasks.
What each says it does
pw
Production-grade Playwright testing toolkit. 9 skills, 3 agents, 55 templates, TestRail + BrowserStack MCP integrations. Generate tests, fix flaky failures, migrate from Cypress/Selenium.
io.github.kubeshop/testkube-mcp
MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
How to run each
pw
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.kubeshop/testkube-mcp As a local MCP server: Docker image
claude mcp add --env "TK_ACCESS_TOKEN=<YOUR_TK_ACCESS_TOKEN>" --env "TK_ENV_ID=<YOUR_TK_ENV_ID>" --env "TK_ORG_ID=<YOUR_TK_ORG_ID>" --transport stdio testkube -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ENV_ID -e TK_ORG_ID mcp/testkube
Requires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.kubeshop/testkube-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of pw publish no list of tools, so we do not compare tools.
Settings each asks for
Only pw asks for
BROWSERSTACK_ACCESS_KEY (secret)BROWSERSTACK_USERNAMETESTRAIL_API_KEY (secret)TESTRAIL_URLTESTRAIL_USER
Only io.github.kubeshop/testkube-mcp asks for
TK_ACCESS_TOKEN (secret)TK_CONTROL_PLANE_URLTK_DASHBOARD_URLTK_DEBUGTK_ENV_ID (secret)TK_MCP_SHTTP_AUTH_TOKEN (secret)TK_ORG_ID (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: pw · What it can do: io.github.kubeshop/testkube-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.