AI Subroutines vs Safari MCP

AI Subroutines from rtrvr.ai are a new automation primitive: you record a browser task once (a form submission, a LinkedIn connection, a CRM update), and that recording becomes a deterministic, callable tool that AI agents can invoke with different parameters — without spending tokens on every run. Unlike Playwright, Browser-Use, or other out-of-process solutions, Subroutines execute entirely inside your browser tab, inheriting your live session cookies, CSRF tokens, and signed headers automatically. The technical approach is clever. During recording, the system captures network requests and DOM interactions, then ranks captured requests to identify the actual API call (filtering out analytics and telemetry). Replay-hostile identifiers are stripped while stable endpoints are preserved. The result is a script that runs in your browser context — no session rebuilding, no key extraction, no proxy rotation needed. The AI handles parameter selection; the script handles execution. The business case is clear for outreach and operations teams: bulk LinkedIn campaigns, CRM mass-updates, scraping pipelines, and form submissions that would cost hundreds of tokens per run instead execute as cheap deterministic scripts. The model positions Subroutines as the "function call" layer beneath AI agents — the actions that don't need intelligence every time they fire.

Safari MCP is an open-source Model Context Protocol server that exposes 80 native macOS tools for automating Safari — covering everything from tab management and form filling to JavaScript execution, screenshot capture, and network request interception. Unlike Playwright or Puppeteer which spin up a Chromium subprocess, Safari MCP connects directly to a running Safari instance through AppleScript and the macOS Accessibility APIs, making it the only browser automation option that works with your actual logged-in Safari session, cookies, and extensions intact. The 80-tool scope is notable: most browser MCP implementations ship 10–20 tools focused on basic navigation. Safari MCP covers the full browser lifecycle — bookmark management, reading list, private browsing, download tracking, and even Safari's built-in translation feature. For macOS-heavy teams where Safari is the default browser (and where Chrome-based automation feels like bringing in a chainsaw to peel an apple), this fills a practical gap. It appeared on Hacker News with a small but enthusiastic audience — primarily macOS devs who've been watching the Chrome-centric browser automation ecosystem with mild frustration. The zero-dependency installation (no browser binary downloads, no npm build step) and the fact that it leverages Apple's own accessibility stack rather than reverse-engineering the browser protocol makes it an unusually clean approach.