Let AI Control Your Real Browser — Not a Throwaway One

Most browser MCP servers launch a separate browser instance. Clean slate, no cookies, no auth. Want to automate something behind a login? Re-authenticate every time. Want to test your actual session state? Too bad. What if the AI could just use the browser you already have open? That's what Dramaturg + @playwright-repl/mcp does. The AI controls your real Chrome tabs — your cookies, your sessions, your localStorage — all intact. How it works Claude (or any MCP client) ↕ MCP (stdio) playwright-repl MCP server ↕ WebSocket Dramaturg Chrome extension ↕ CDP / chrome.debugger Your real Chrome tabs The key difference: Playwright runs inside the browser, not outside it. The extension uses playwright-crx to run the full Playwright API directly in Chrome's service worker. No Node.js relay, no separate browser process. This means: No re-authentication — Gmail, Notion, your internal tools — already logged in expect() assertions — something no other browser MCP server supports You see everything — t