MCP.so
Sign In
C

Claude For Safari

@Lyosis

About Claude For Safari

Safari Web Extension + Node.js MCP bridge giving Claude Desktop full control over Safari — navigate, read pages, click elements, fill forms, and manage tabs. No Playwright or WebDriver dependency.

Basic information

Category

AI & Agents

Transports

stdio

Publisher

Lyosis

Submitted by

wilfrid

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "safari": {
      "command": "node",
      "args": [
        "/path/to/claudeForSafari/bridge/bridge.js"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Claude For Safari?

Claude For Safari is an MCP server that gives Claude Desktop the ability to control Safari — navigate pages, read content, click elements, and fill forms — just like "Claude in Chrome." It is built for macOS users who want to automate Safari through Claude Desktop.

How to use Claude For Safari?

Clone the repository, install bridge dependencies with npm, build the Safari extension in Xcode, enable the extension in Safari settings, and add the server entry pointing to bridge/bridge.js in your claude_desktop_config.json. Safari must be open with the extension enabled; the bridge starts automatically with Claude Desktop.

Key features of Claude For Safari

  • 13 tools for Safari control including navigation, reading, and clicking
  • Execute arbitrary JavaScript in the active tab
  • List, create, close, and switch between tabs
  • Read visible page text or full HTML
  • Fill form input and textarea fields
  • Find elements by CSS selector or text content
  • Support for multiple Safari profiles

Use cases of Claude For Safari

  • Automate web data extraction and page reading through Claude Desktop
  • Fill and submit web forms programmatically
  • Navigate multi-step workflows across tabs and profiles
  • Scrape or test web content using JavaScript execution
  • Replicate Chrome automation workflows in Safari

FAQ from Claude For Safari

What makes Claude For Safari different from other browser automation tools?

It gives Claude Desktop the same Safari control that "Claude in Chrome" provides for Chrome, using the MCP protocol.

What are the system requirements?

macOS 14+ (Sonoma or later), Xcode 16+, Node.js v18+, an Apple developer account (free is sufficient), and Claude Desktop with MCP support.

Where does data processed by the server live?

The bridge listens on localhost only (ws://localhost:45678) and is never exposed to the network. Data stays entirely on your machine.

What are known limitations?

safari_form_input does not support rich text editors using contenteditable (e.g., Notion, Gmail compose). safari_get_page_text fails on internal Safari pages such as favorites:// or about:blank.

How does authentication and transport work?

Transport uses MCP stdio between Claude Desktop and the bridge, then WebSocket between the bridge and the Safari extension. There is no cryptographic authentication between the bridge and extension; any local process can connect to the port, so the threat model assumes other processes under your user account are trusted.

Comments

More AI & Agents MCP servers