Add persistent browser state/cookie configuration to built-in Playwright MCP server

Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Title:

Add persistent browser state/cookie configuration to built-in Playwright MCP server

Description:

Problem

The built-in cursor-playwright MCP server launches fresh browser instances without persistent state, making it impossible to access authenticated sessions (Google Docs, GitHub, internal company tools, etc.).

Proposed Solution

Add configuration options in Cursor settings for the built-in Playwright MCP server:

"cursor.playwright.storageState": "/path/to/auth-state.json"

or

"cursor.playwright.userDataDir": "/Users/<username>/Library/Application Support/Google/Chrome/Default"

Why This Matters

  • External MCP servers like @browsermcp/mcp already support persistent profiles and work with authenticated sessions
  • Standard Playwright supports this via launchPersistentContext and storageState
  • Would enable AI to interact with authenticated tools without manual workarounds

Use Cases

  • Accessing authenticated internal company tools
  • Testing features behind login
  • Reading/interacting with Google Workspace documents
  • Maintaining consistent browser state across sessions

Operating System (if it applies)

MacOS

2 Likes
2

Are there any updates on this?