Support

Safari only discovers extensions bundled inside an app that has been launched at least once.

• Make sure you’ve opened Claude Safari Connector at least once after installing it.
• Restart Safari fully — Command-Q, not just closing windows.
• If the extension still doesn’t appear, check that the app is in your Applications folder. Running it from Downloads or a disk image may prevent Safari from registering the extension.

The most common cause is that Claude wasn’t restarted after the connection was set up.

1. Quit Claude Code or Claude Desktop fully — Command-Q, or right-click the Dock icon and choose Quit.
2. Relaunch it.
3. In Claude Code, run /mcp to confirm the mcp__claude-in-safari__* tools appear.

If the tools still don’t appear, check the app’s Status tab. If it shows “Path mismatch”, click “Update path…” and restart Claude again.

The toolbar button sends a signal to Claude Safari Connector. If the app isn’t running, nothing happens.

• Make sure Claude Safari Connector is running — look for it in the Dock or the menu bar.
• If the app is running but the button still does nothing, check that the extension is enabled in Safari → Settings → Extensions.

This means Accessibility permission hasn’t been granted (or was denied). Accessibility lets the app send real mouse and keyboard input to Safari.

1. Open System Settings → Privacy & Security → Accessibility.
2. Find “Claude Safari Connector” in the list. If the toggle is off, turn it on. If it doesn’t appear, click “+” and navigate to the app in Applications.
3. After granting Accessibility, quit Claude Safari Connector completely and relaunch it. macOS caches permission decisions per process — the app must restart before the new permission takes effect.

Keyboard tools (type, key) will not work without this permission. Mouse tools will fall back to a less reliable method — some sites may ignore those fallback clicks.

macOS stores permission decisions for the specific running process. When you grant a permission, the app needs to restart before it reads the updated decision.

Quit the app completely and relaunch it. The status in the Permissions tab should update to “Granted” after the relaunch.

If you moved the app (for example, from Downloads to Applications) after granting the permission, macOS may treat it as a different app and you’ll need to grant the permission again.

If you clicked “Don’t Allow” when macOS asked whether Claude Safari Connector can control Safari, you can re-enable it in System Settings:

1. Open System Settings → Privacy & Security → Automation.
2. Find “Claude Safari Connector” in the list.
3. Make sure the toggle next to “Safari” is turned on.

If “Claude Safari Connector” doesn’t appear in that list, try asking Claude to use a Safari tool (for example, resize the window). macOS will prompt again, and you’ll have a chance to click Allow.

Sites can detect whether a click came from a real person or a script. Claude Safari Connector uses two methods:

• Trusted input — when Accessibility is granted and Safari is the active window, clicks are delivered as real OS-level input. Sites cannot distinguish these from physical mouse clicks.
• Fallback input — when the trusted path isn’t available, clicks are injected through the page’s scripting engine. Some sites check for this and ignore it.

Make sure Accessibility permission is granted (see above), then quit and relaunch the app. Sites with aggressive anti-bot protection may still reject input in some circumstances — this is a known limitation.

• Check that the Safari extension is still enabled in Safari → Settings → Extensions. If it was disabled during a session, tool calls will time out because there’s nothing in Safari to respond.
• Restart Claude Code or Claude Desktop. If the session ran for a long time or the app was restarted mid-session, the connection may have dropped. A full restart re-establishes everything cleanly.
• Check that Claude Safari Connector is running. Find it in the Dock or the menu bar.

Uninstalling has two parts:

1. Remove the app. Drag “Claude Safari Connector” from your Applications folder to the Trash.

2. Remove the MCP server entry from your Claude config. The app added itself to your config file when you clicked “Connect to Claude”. Remove it manually, otherwise Claude will try to launch a binary that no longer exists each time it starts.

   • Claude Code: open ~/.claude.json and remove the "claude-in-safari" entry from the "mcpServers" section.
   • Claude Desktop: open ~/Library/Application Support/Claude/claude_desktop_config.json and remove the same entry.

After removing the config entry, restart Claude Code or Claude Desktop.

Email craig@rungie.com with:

• Your macOS version (Apple menu → About This Mac)
• Your Safari version (Safari menu → About Safari)
• The app version (visible in the app’s Settings tab or title bar)
• Steps to reproduce — what you asked Claude to do, what happened, and what you expected
• Any error message Claude reported, copied verbatim