I replaced Chrome DevTools MCP with Safari on my Mac. Here's what happened.

Everyone in the MCP world uses Chrome. I stopped. Not because I'm contrarian. Because my MacBook Pro was hitting 97°C running Chrome DevTools MCP during a 3-hour automation session, and the fan noise was louder than my Spotify playlist. I'm an automation developer who builds AI-powered workflows for businesses (achiya-automation.com). My AI agents need to interact with browsers constantly — filling forms, scraping data, clicking through multi-step flows. Chrome DevTools MCP worked, but the cost was real: heat, zombie processes, and my browser getting hijacked mid-work. So I built Safari MCP — a native macOS MCP server with 80 tools, running entirely through AppleScript and JavaScript. No Chrome. No Puppeteer. No Playwright. Here are 7 things I learned along the way. 1. WebKit on Apple Silicon is dramatically cheaper than Chromium This isn't a fabricated benchmark — it's something any Mac developer can verify themselves. Safari uses the native WebKit engine that Apple optimizes specific