Skip to main content
Glama

Related Servers

Alternatives to Safari MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents drive your real, already-logged-in browsers on macOS in the background without stealing focus, organizing work into tab groups, reading pages as compact accessibility snapshots, and saving repeatable scenarios. Supports Chrome, Edge, Brave, Yandex Browser, and Safari, with per-agent isolation and automatic tab cleanup.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Native macOS browser (SwiftUI + WKWebView) that exposes an MCP server in-process so AI agents can drive a real local browser with the user's existing logged-in sessions. ~40 tools (navigate, click, fill, screenshot, eval_js, network log, accessibility tree). Local-only with bearer-token auth.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with Safari browser automation and developer tools access, enabling LLMs to control Safari, access console logs, monitor network activity, and perform browser automation tasks.
      13
      9 npm
      33
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Native WebKit browser automation for MCP agents on Apple silicon Macs (macOS 15+), with persistent sign-ins, human approval and local handoff. Runs locally through a companion app; Developer Preview under BUSL-1.1, with a separate agreement required for commercial production use.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight browser automation server for AI agents, enabling fast (10-25ms per action), structured observations and semantic selectors with zero token overhead.
      6
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      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.
      4
      13
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 98 tools

    Disambiguation3/5

    The set contains many near-duplicate interaction primitives (safari_click, safari_native_click, safari_click_and_read, safari_click_and_wait, safari_double_click/right_click; safari_fill vs safari_type_text vs safari_native_type) plus multiple page-reading tools. Descriptions largely explain when to use each, so boundaries are recoverable, but the sheer number of options creates real misselection risk.

    Naming Consistency5/5

    All 98 tools use the safari_ prefix and snake_case, with predictable verb/object naming for most (safari_click, safari_navigate, safari_get_cookies). A few noun-style names (safari_snapshot, safari_doctor, safari_network) are minor deviations, not convention mixing.

    Tool Count1/5

    98 tools is far beyond a well-scoped browser automation surface; many are specialized variants (native_*, *_and_read/wait, storage/console/network micro-tools). Even if individually useful, this is an extreme tool-count mismatch for agent selection.

    Completeness5/5

    Coverage is exceptionally broad: navigation, interaction, forms, storage, cookies, network mocking/capture, console, screenshots, accessibility, PWA, CSS coverage, emulation, iframes, uploads, and dialogs. No obvious lifecycle gap for browser automation.

    Maintenance

    ActivityActive
    ResponsivenessResponsive