Safari Mcp
Automate the native Safari browser from Claude Code or Cursor on Mac with 80 MCP tools and without running Chrome.
Overview
Safari MCP is a MCP server for the Build phase that provides 80 native Safari browser automation tools for coding agents over stdio without Chrome.
What is this MCP server?
- 80 native Safari automation tools exposed via MCP
- Zero Chrome overhead—uses macOS Safari directly
- npm package safari-mcp v2.9.3 with stdio transport
- Registry: io.github.achiya-automation/safari-mcp
- GitHub: achiya-automation/safari-mcp
- 80 browser automation tools per server description
- Package version 2.9.3 on npm identifier safari-mcp
- Transport: stdio MCP
Community signal: 111 GitHub stars.
What problem does it solve?
Chrome-based browser MCP stacks add overhead and miss real Safari/WebKit behavior when you automate testing and research on a Mac.
Who is it for?
Mac-based indie builders who live in Safari and want agent-driven browser automation from Claude Code, Cursor, or similar without a Chrome stack.
Skip if: Windows or Linux developers, teams standardized on headless Chrome-only CI, or anyone unwilling to give an agent full browser control on their machine.
What do I get? / Deliverables
After installing safari-mcp via npm and enabling stdio MCP, your agent can control Safari through 80 documented tools for flows you define.
- 80-tool Safari control surface available to the agent
- Local browser automation without Chrome runtime dependency
Recommended MCP Servers
Journey fit
Build/integrations is canonical because browser MCP is wired while implementing agent-driven QA, scraping, or UI flows in the product toolchain. integrations captures external browser control as an agent tool surface, distinct from writing frontend components in isolation.
How it compares
Native Safari stdio automation with 80 tools, not a cloud browser farm or on-chain agent safety API.
Common Questions / FAQ
Who is Safari MCP for?
Solo Mac developers using AI coding agents who need real Safari automation instead of Chromium-only browser MCP servers.
When should I use Safari MCP?
Use it during Build integrations when you implement agent-driven browsing, WebKit-specific checks, or local QA loops tied to Safari.
How do I add Safari MCP to my agent?
Install the npm package safari-mcp (v2.9.3), add the stdio MCP server io.github.achiya-automation/safari-mcp to your agent config, and run on macOS with Safari available.