# Kernel vs Playwright MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/kernel-vs-playwright-mcp.md (~4,450 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/kernel-vs-playwright-mcp.json · canonical https://www.anchorterminal.com/compare/kernel-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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Kernel scores 66.9 (B) on agent readiness against Playwright MCP's 63.7 (B), and leads in 4 of 7 scored categories. Playwright MCP leads on transparency & trust. Both do browser automation.

- Kernel: B 66.9, rank #352 of 1510 · https://www.anchorterminal.com/tools/kernel.min.md
- Playwright MCP: B 63.7, rank #502 of 1510 · https://www.anchorterminal.com/tools/playwright-mcp.min.md
- Kernel, good for Agents that need hosted, logged-in browsers at scale with stealth and proxies. browserbase, steel, hyperbrowser and anchor-browser are the nearest listings. Ahead on Schema & documentation, 93 against 70; Security & auth, 81 against 57; Payments & pricing, 65 against 60; Maintenance & community, 90 against 84. Also A hosted endpoint, with nothing to install.
- 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 Transparency & trust, 74 against 61. Also No key needed to call it; Runs on your own machine; Open source.

| Category | Kernel | Playwright MCP |
| --- | --- | --- |
| Reliability (16%) | 53 | 57 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 70 |
| Agent ergonomics (13%) | 84 | 84 |
| Security & auth (14%) | 81 | 57 |
| Payments & pricing (10%) | 65 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 90 | 84 |
| Transparency & trust (7%) | 61 | 74 |

| Fact (where they differ) | Kernel | Playwright MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Kernel Technologies, Inc. | Microsoft |
| Hosted endpoint | `https://mcp.onkernel.com/mcp` | no (local only) |
| Transports | Streamable HTTP | stdio, Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Free |
| Licence | none | Apache-2.0 |
| Tools exposed | 32 | 72 |
| llms.txt | yes | no |
| MCP registry | `com.onkernel/kernel-mcp-server` | `io.github.microsoft/playwright-mcp` |
| Last release | 2026-11-06 | 2026-10-31 |
| Terms last updated | 2026-09-01 | no document linked |
| Privacy policy last updated | 2026-09-15 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | none | 37k stars, 5.3M npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Security & auth, Kernel +24: Kernel 81 (Scoped API keys with resource and action policies, project scoping and expiry, and OAuth 2.1 for MCP with project-limited tokens (30). Least privilege through scoped keys, a payment cap for cards through the MCP server and vault writes that need their own action (16). Pages an agent browses are untrusted, and we found no prompt-injection guidance in the docs read (4). Audit log search and export on Start-Up and above (13). SOC 2 Type II, HIPAA, PCI DSS and ISO 27001 on the security page and a HackerOne bounty (18). 30 + 16 + 4 + 13 + 18 = 81, before the deduction for the November 2026 incident.); Playwright MCP 57 (No credentials to leak and nothing to scope, so the middle band (20). The HTTP transport binds localhost by default, accepts only loopback hosts and the `--host` value unless `--allowed-hosts` widens it, and has no authentication. File access is limited to workspace roots unless `--allow-unrestricted-file-access`, with symlinks resolved since v0.0.81, and `--secrets` and `--redact-url-params` mask values in responses. `--isolated` is off by default, the allowed and blocked origin lists say they aren't a security boundary, `browser_run_code_unsafe`, described in its own text as RCE-equivalent in the server process, sits in the core set that can't be switched off, and on Linux the downloaded Chromium builds (`--browser chromium`, and since v0.0.81 a config naming `chromium` with no channel) launch without the Chromium sandbox unless `--sandbox` is set, while the default Chrome channel keeps it (10). Page content is untrusted and we found no prompt-injection guidance beyond a README line that the server isn't a security boundary and a release note to treat WebMCP tools as untrusted input (0). `--save-session`, traces, video and generated Playwright code for each action give the operator a record (12). Microsoft's MSRC reporting policy in SECURITY.md, and one advisory published, CVE-2025-9611 (High, fixed in v0.0.40) (15).)
- Schema & documentation, Kernel +23: Kernel 93 (OpenAPI at kernel.sh/openapi.json and per-endpoint Markdown reference (25). llms.txt with 423 entries and a Markdown twin for each page (10). Endpoint descriptions say when to use alternatives ("For interactive browsing, use GET /audit-logs", pools for bursty traffic) (17). Typed parameters with enums and limits such as memory sizes and timeout maximums (13). Code samples in TypeScript, Python and Go, and documented status codes such as 409 and 204 on pool acquire (13). A dated public changelog and SDK changelogs (15). 25 + 10 + 17 + 13 + 13 + 15 = 93.); 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).)
- Transparency & trust, Playwright MCP +13: Kernel 61 (The platform is closed under a published master services agreement; the MCP server is MIT (20). The privacy policy names Stripe and Google Analytics and an advertising cookie, and states retention as long as needed, with replay retention per plan and zero data retention on Enterprise (18). Deprecated MCP inputs stay as aliases and the changelog notes removals, but no deprecation policy (10). No sub-processor list found; compliance reports sit behind the trust centre (10). 20 + 18 + 10 + 10 = 58.); 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).)
- Maintenance & community, Kernel +6: Kernel 90 (The changelog's latest entry is 16 October 2026 and the MCP server repository has commits on 6 November (30). More than three dated changes in 90 days, scoped keys, memory tiers, GPU tier and card payments among them (20). A closed service with a public changelog, Discord, email support and an open-source MCP server with 210 commits since 8 August (15). Official SDKs in three languages, and the MCP server in the registry as com.onkernel/kernel-mcp-server 1.1.0 (15). CI and tests in the MCP repository (10). 30 + 20 + 15 + 15 + 10 = 90.); 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).)
- Payments & pricing, Kernel +5: Kernel 65 (MPP on POST /mpp/browsers, a 402 challenge paid with a Stripe shared payment token through Link, covering one browser product only, not the API or MCP server (20). Per-second prices public without a login (20). The Developer plan is free with $5 of monthly credit, but whether signup needs a card wasn't stated on the pages read (10). Through MPP an agent gets a browser with no account or key, though a person approves each Link payment (15). 20 + 20 + 10 + 15 = 65.); Playwright MCP 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).)