Or: why every browser-automation MCP uses Chromium, and why that's the wrong default on macOS. The problem I kept hitting Every browser automation MCP server I tried on my Mac — chrome-devtools-mcp, playwright-mcp, browsermcp, puppeteer-mcp — did the same thing: spin up a fresh Chromium instance with nothing in it. No logins, no cookies, no session state. Then my AI agent would spend the first 5
I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked)
אחיה כהן·Dev.to··1 min read
D
Continue reading on Dev.to
This article was sourced from Dev.to's RSS feed. Visit the original for the complete story.