[FEATURE] Playwright mcp server integration

Resolved 💬 2 comments Opened Apr 17, 2026 by vahagnhovhannisyan-soft Closed Jun 4, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When multiple users connect to a shared Playwright MCP server, all session artifacts are written to the same .playwright-mcp/ folder on the server:

server/.playwright-mcp/
page-userA-snapshot.yml ← contains full page content of User A's session
page-userB-snapshot.yml ← contains full page content of User B's session
console-userA.log
console-userB.log
There is no isolation between users. Snapshots contain the full accessibility tree of the page being tested, which may include sensitive data such as PII, financial information, or credentials. User A's Claude Code session can read User B's snapshot file, causing unintended data leakage with no visibility and no way to prevent it.

Proposed Solution

Scope all .playwright-mcp/ artifacts to a per-session or per-user isolated directory on the server:

server/.playwright-mcp/
session-userA/
page-xxx.yml
console-xxx.log
session-userB/
page-xxx.yml
console-xxx.log
Each user's artifacts are isolated. No cross-user file access is possible.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗