**1. MCP enables cross‑browser automation, especially for Safari**
"Having an MCP server for it could fill a real gap in cross‑browser testing for agent workflows." — jickmao
**2. Testing Safari without Apple hardware is a major hurdle**
"How do you test on Safari if you don’t have Apple devices?" — demetris
**3. Naming, marketing and AI‑tooling attitudes shape community reaction**
"Not sure you want to hear this but there is 0% chance I will ever bring up a product with a vulgar name at work." — keepamovin
The Safari MCP server for web developers
📝 Discussion Summary (Click to expand)
🚀 Project Ideas
SafariAgent Cloud
Summary
- Provide a hosted MCP server for Safari that developers can invoke via API to control real iOS/macOS Safari instances for automated browser testing, eliminating the need for personal Apple hardware.
- Enables AI agents to reliably test web pages across Safari’s unique WebKit behavior without local macOS VMs.
Details
| Key | Value |
|---|---|
| Target Audience | AI developers, QA engineers, cross‑browser testers |
| Core Feature | Remote Safari MCP endpoint with session management, screenshot, DOM manipulation, and performance profiling |
| Tech Stack | Backend: Node.js + Python FastAPI; Hosted on AWS Fargate; Uses Apple‑provided safaridriver in Docker; Redis for session state |
| Difficulty | High |
| Monetization | Revenue-ready: pay‑per‑minute compute (e.g., $0.02/min) + optional enterprise tier |
Notes
- HN users repeatedly asked for a “real Safari testing service” without owning a Mac; this solves that directly.
- Offers built‑in Private Relay IP whitelisting to bypass scraping blocks, addressing a specific concern raised.
- Could integrate with existing LLM pipelines, making it a natural extension for agent workflows.
Unified Browser RPC Bridge
Summary
- A lightweight RPC layer that aggregates Chrome, Firefox, and Safari MCP servers behind a single, typed API, allowing agents to switch browsers seamlessly.
- Handles safety checks and auto‑retries, reducing the “edgy” friction noted by participants.
Details
| Key | Value |
|---|---|
| Target Audience | LLM agents, browser automation frameworks, developer tooling startups |
| Core Feature | Unified API endpoints (/click, /evaluate, /inspect) that internally route to appropriate MCP server, with built‑in feature detection |
| Tech Stack | TypeScript client; Go server exposing REST + WebSocket; Dockerized micro‑services per browser |
| Difficulty | Medium |
| Monetization | Revenue-ready: subscription $19/mo per seat (self‑hosted or SaaS) |
Notes
- Directly addresses the need expressed for “a sane crossover of dev tools and LLM” and the desire for “cross‑browser parity”.
- Community discussion highlighted the lack of Safari support; this bridge can expose a Safari MCP server automatically.
- Could be packaged as an open‑source CLI and a hosted SaaS, appealing to both hobbyists and commercial users.
WebKitMobile Simulator CLI
Summary
- A CLI tool that spins up a headless WebKit (iOS Safari) instance via Playwright or WebKit‑GTK, exposing a MCP server that mimics mobile Safari behavior for AI agents.
- Enables realistic mobile testing, including viewport, touch events, and Private Relay simulation.
Details
| Key | Value |
|---|---|
| Target Audience | AI developers, mobile web QA, cross‑device testers |
| Core Feature | Mobile‑Safari emulator with touch simulation, network throttling, and Private Relay IP whitelist injection |
| Tech Stack | Rust binary; WebKitGTK; Docker container; exposes MCP over stdio |
| Difficulty | Medium |
| Monetization | Hobby |
Notes
- Responds to the specific request “Building something similar for Chrome and Firefox browsers... considering MCP for distribution” and the question about mobile simulator Safari.
- Users asked “Does this support mobile simulator safari too?” This tool directly answers that.
- Low barrier to entry for hobbyists; could be packaged as a GitHub Action for CI pipelines.