# Kane CLI vs Playwright MCP (slim)

> Playwright MCP scores 63.7 (B) to Kane CLI's 55.3 (C) for browser automation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kane-cli-vs-playwright-mcp.md (~5,150 tokens) · this version ~2,980 tokens · JSON https://www.anchorterminal.com/compare/kane-cli-vs-playwright-mcp.json · canonical https://www.anchorterminal.com/compare/kane-cli-vs-playwright-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Playwright MCP scores 63.7 (B) on agent readiness against Kane CLI's 55.3 (C), and leads in 6 of 7 scored categories. Kane CLI leads on schema & documentation. Both do browser automation.

- Kane CLI: C 55.3, rank #805 of 1260 · https://www.anchorterminal.com/tools/kane-cli.min.md
- Playwright MCP: B 63.7, rank #433 of 1260 · https://www.anchorterminal.com/tools/playwright-mcp.min.md
- Kane CLI, good for Coding agents and CI that need to check a web or mobile app in a real browser or device and keep replayable Markdown tests with evidence. Ahead on Schema & documentation, 77 against 70. Also No incidents deducted, where Playwright MCP loses 4 points for them.
- Playwright MCP, good for The default choice for an agent that drives web pages by structure rather than pixels. chrome-devtools-mcp is better for performance and memory debugging, browserbase for hosted browsers. Ahead on Reliability, 57 against 50; Agent ergonomics, 84 against 65; Payments & pricing, 60 against 20; Maintenance & community, 84 against 77; Transparency & trust, 74 against 38. Also No key needed to call it; Runs on your own machine; Open source.

| Category | Kane CLI | Playwright MCP |
| --- | --- | --- |
| Reliability (16%) | 50 | 57 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 70 |
| Agent ergonomics (13%) | 65 | 84 |
| Security & auth (14%) | 55 | 57 |
| Payments & pricing (10%) | 20 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 77 | 84 |
| Transparency & trust (7%) | 38 | 74 |

| Fact (where they differ) | Kane CLI | Playwright MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | TestMu AI (formerly LambdaTest) | Microsoft |
| Transports |  | stdio, Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | None |
| Pricing | Paid | Free |
| Licence | The npm wrapper, skill and repository are Apache-2.0. The runner, assurance and pinned Node binaries it installs are labelled Apache-2.0 on npm, but their source isn't in the linked repository. TestMu AI's service terms weren't read | Apache-2.0 |
| Tools exposed | none | 72 |
| MCP registry | not listed | `io.github.microsoft/playwright-mcp` |
| Last release | 2026-10-28 | 2026-10-31 |
| Popularity | 2.1k npm/wk | 37k stars, 5.3M npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Payments & pricing, Playwright MCP +40: Kane CLI 20 (No x402, MPP or L402 (0). Plan prices are public per the listing check of 1 November 2026 (Starter $17 a month billed annually, Pro $89), and `run_end` reports credits per run, but the credit price per run isn't published, so plan-only pricing (10). The release says "free to start" and the check found a 10,000-credit, 30-day trial; whether it needs a card couldn't be read today. Judgement call (10 of 20). A person signs up and approves OAuth in a browser, or copies an access key from the dashboard, before any run (0).); Playwright MCP 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).)
- Transparency & trust, Playwright MCP +36: Kane CLI 38 (The editorial half. The wrapper, skill and docs are Apache-2.0. The runner, assurance and pinned Node binaries are labelled Apache-2.0 on npm with no source in the linked repository, and the service terms couldn't be read (12 of 30). The repository says what leaves the machine. Every run uploads to Test Manager with screenshots and an evidence pack recording the user's name and email, secrets are masked, credentials are stored with mode 0600, and the evidence viewer reads packs locally. The privacy policy, DPA and retention periods are on testmuai.com and weren't read (10 of 30). The changelog calls out breaking changes, such as the removal of the bare-objective shortcut in 0.4.1, but there's no deprecation policy or dated notice period (5 of 20). The changelog describes telemetry (a remote log, support ids, errors spooled and sent at exit) and a daily npm update check. The opt-out `KANE_TELEMETRY=0` appears only in a skill reference, not the user guide (8 of 20).); Playwright MCP 74 (Apache-2.0 (30). Local software. There's no written data statement, but we found no telemetry or remote calls beyond the pages it's asked to open in the MCP code (20). No deprecation policy, and 0.0.x versioning gives no notice of tool renames (5). No telemetry in the source we read (20).)
- Agent ergonomics, Playwright MCP +19: Kane CLI 65 (Graded on the CLI as an agent drives it. `run_end` carries `summary`, `one_liner` and only the values asked for with "store as" in `final_state`, and `--max-steps` and `--timeout` bound a run. The skill an agent loads is about 40 KB with 25 reference files (15 of 25). `testrun` selects by paths, `--match` and `--tags`, `explore list` and `explore sessions` filter by run, and `--json` on design and review commands; few size controls beyond that (14 of 20). Exit codes separate pass, fail, setup error and timeout, failure reasons are named, and refusals name the command to run next (18 of 20). Replays of saved tests come from cache, reconcile resumes rather than re-billing, and Exploration allows one run at a time. A one-shot `run` has no idempotency key and Exploration's default can change data (10 of 20). One required argument for `run`; Exploration's `mutating` default isn't a safe one; no SDKs, only the CLI from npm, Homebrew and a shell script (8 of 15).); Playwright MCP 84 (72 tools in the README across ten groups. Only core and tabs load by default, 25 tools (15). `--caps` adds network, storage, devtools, vision, PDF, testing and config groups only when asked, and `--snapshot-mode none` and `--image-responses omit` trim each response (plus 10). `browser_find` searches the snapshot instead of returning it and takes `maxResults` since v0.0.84, snapshots take `depth`, and most read tools can write to a file instead of the response (17). Modal-state errors name the tool that clears them (14). Every tool carries `readOnlyHint`, `destructiveHint` and `openWorldHint`, 29 marked read-only. Every other tool is marked destructive, hover included, which blunts the signal (18). Few required parameters and defaults that work. npm and Docker only (10).)
- Reliability, Playwright MCP +7: Kane CLI 50 (Graded with the hosted lines, because every run, exploration and design job goes through TestMu AI's service and spends credits, and Exploration runs on HyperExecute. status.lambdatest.io (Statusfy) lists Kane CLI and KaneAI as their own components with incident history and an Atom feed (20). From 3 August to 1 November 2026 no incident names Kane CLI or KaneAI. The platform under it had test creation timeouts from 09:00 to 13:30 UTC on 28 September with slow Automation and HyperExecute starts, six hours of partial macOS HyperExecute degradation on 25 September, and real-device partial outages on 21 August and 22 October (57 minutes). Judgement call, 10 for multi-hour degradation of the service runs depend on. No request rate limit is published; the only numbers are Exploration's built-in limits (an hour, 400 actions or 800 model calls), 20 cloud browsers and a 15-minute real-device queue (5 of 15). No 429 or Retry-After guidance. `maintain reconcile` is documented as idempotent, Exploration refuses a second run with `RUN_ACTIVE`, and the skill says never to rerun a paid command just to get a support id (5 of 15). No SLA found; the terms weren't readable (0). Nothing in the repository labels Kane CLI or Exploration beta or preview (10).); Playwright MCP 57 (Scored as a local stdio package (it also serves HTTP with `--port`). Official npm package @playwright/mcp with Node 18 or later stated. It pins alpha builds of Playwright (1.65.0-alpha-2026-10-30 in v0.0.84) as dependencies (20). CI runs lint, tests on Ubuntu, macOS and Windows and a Docker test on every push and pull request. Most MCP tests live in the main Playwright repository. We didn't see the run status, so 20 of 25. Issues have been redirected to microsoft/playwright since 29 June 2026, and GitHub's robots rules blocked our search there, so we couldn't count open crash reports (12). Versions run 0.0.x with release notes on GitHub but no semver meaning (5). Not 1.0 and not declared stable (0).)
- Schema & documentation, Kane CLI +7: Kane CLI 77 (No OpenAPI or JSON Schema file. The NDJSON events are documented in typed Markdown tables, `run_end` is declared stable across versions, and each command family has its event list (10 of 25). Markdown docs in the repository, an agent skill and a context7.json for agents. The agents.md guide on testmuai.com wasn't readable and no llms.txt was checked (10). The user guide and skill say when to use `run`, `testmd`, `testrun`, assurance or Exploration, and when not (Exploration when there are no written requirements, `read_only` for data you care about) (17 of 20). Flag tables give defaults and allowed values for `--mode`, `--target`, `--policy` and `--bug-detection`; `--variables` and `--session-context` take free-form JSON (12 of 15). Examples throughout, exit-code tables and troubleshooting tables with named failures such as `failed:setup_failed` and `RUN_ACTIVE`. The README's `run_end` example names `credits` while the skill names `credits_consumed` (13 of 15). Semantic versions with a dated Keep a Changelog file and git tags (15).); Playwright MCP 70 (Every tool's input is a Zod schema turned into JSON Schema (25). The README's tool list is generated from the source. No llms.txt (5). Descriptions are mostly one line, "Perform click on a web page" or "Returns all console messages". `browser_find` and `browser_snapshot` explain when they're cheaper, and the README says when to prefer the CLI over MCP (10). Enums for mouse buttons, modifiers and console levels, `depth` on snapshots, and a free-form MIME map on `browser_drop` (13). Few examples beyond `browser_run_code_unsafe` and `browser_find`, and no documented error list (7). GitHub release notes for each 0.0.x version (10).)
- Maintenance & community, Playwright MCP +7: Kane CLI 77 (0.10.0 on npm on 28 October 2026, 4 days ago (30). 28 releases from 3 August to 1 November 2026, 0.8.4 to 0.10.0, each in the changelog (20). The repository has 337 commits, pull requests up to #222 merged within days by LambdaTest staff, a Discord and an issue tracker. GitHub's API wasn't reachable from this session, so open issues and reply times weren't counted (12 of 25). Not an MCP server. The CLI and skill are current on npm and a Homebrew tap, with no SDK (10 of 15). CI runs the skill installer's tests on Linux, macOS and Windows with Node 18 and 22. The CLI's own source and tests aren't public, and the main package carries no npm provenance attestation while the skill package does (5 of 10). Kane CLI is six and a half months old by its first npm release.); Playwright MCP 84 (v0.0.84 on 2026-10-31 (30). Six releases since 3 August, v0.0.79 to v0.0.84 (20). Issues moved to microsoft/playwright on 29 June 2026 with a pinned notice. We couldn't read the MCP issues there, and Dependabot pull requests here merge within days (12). Published to the official MCP registry as io.github.microsoft/playwright-mcp by an OIDC workflow on each release, and the registry lists 0.0.84 as latest, published 31 October 2026 (15). Pinned actions and Dependabot, but the package tracks alpha Playwright builds, 1.65.0-alpha-2026-10-30 in v0.0.84 (7).)