Skip to main content
Glama
zhuhroscar-tech

safari-mcp-server

Related Servers

Alternatives to safari-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      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.
      13
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables visual web access and browser automation through Safari, with tools for navigation, screenshots, element interaction, and tab management.
      17
      16 npm
      BSD 3-Clause
    • -
      license
      A
      quality
      Not graded
      maintenance
      A server that provides AI assistants programmatic control of Safari browser on macOS for web automation, testing, and debugging.
      16
      1
      -

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct action: tab-level operations (open, close, tabs) vs. page-level interactions (read, click, fill, js) vs. condition checks (element_exists, wait_for). The only conceivable overlap is between element_exists and wait_for, but one is a one-shot check and the other is a polling operation, so the descriptions make them unambiguous.

    Naming Consistency4/5

    All tools share the consistent 'safari_' prefix and lowercase snake_case style, and most use a verb-like action word (close, read, click, fill, open). Minor deviations exist: 'safari_tabs' is a noun rather than a verb phrase like 'list_tabs', and 'safari_element_exists' is a noun+verb predicate, but the overall pattern remains predictable.

    Tool Count5/5

    Nine tools is a well-scoped size for a Safari automation server, covering navigation, tab management, page reading, and DOM interaction without unnecessary bloat. Each tool earns its place for a focused browser-automation purpose.

    Completeness4/5

    The core workflows are covered: open URLs, read page content, interact via click/fill/JS, wait for elements, and manage tabs. Minor gaps exist, such as no explicit back/forward navigation, no screenshot capability, and no direct 'activate tab' tool, but these are workaroundable and the essential lifecycle of browsing automation is present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues