Achiyacohen

8 ms·

1. 1.▲
   by Achiyacohen 5mo ago

   Author here. Some context that didn't fit in the title. I built safari-mcp a few weeks ago — a macOS-native Safari automation MCP server (no Chrome, no headless, keeps Safari logins). 84 tools via the Model Context Protocol, used direc
2. 2.▲
   Show HN: I benchmarked MCP vs. CLI for browser automation. MCP wins by 25x(github.com)

   2 points by Achiyacohen 5mo ago|1 comments
3. 3.▲
   Show HN: Safari MCP – Native macOS browser automation (80 tools)(github.com)

   5 points by Achiyacohen 5mo ago|1 comments
4. 4.▲
   Safari MCP – Native browser automation for AI agents, 80 tools, ~5ms/cmd(github.com)

   2 points by Achiyacohen 6mo ago|0 comments
5. 5.▲
   by Achiyacohen 6mo ago

   Interesting approach building a dedicated browser for AI agents. The browser-as-infrastructure angle makes sense — most MCP browser servers just wrap Chrome with CDP, which adds significant overhead. One thing I've been thinking about
6. 6.▲
   Safari MCP: 80-tool native browser automation for AI agents (macOS)(github.com)

   1 points by Achiyacohen 6mo ago|0 comments