Skip to main content
Glama
Sign In
safari-browser-mcp

safari-browser-mcp

by Jakub30cz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to safari-browser-mcp

No user-submitted related servers found.

    Related Servers

    • K-Browser

      K-Browserofficial

      kaiwutech-TW
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local AI agents on macOS to drive the user's own signed-in Chrome through their own isolated tabs, with per-client tokens, blocked site categories, masked secrets and human hand-offs. Agents can open and navigate tabs, read pages, send real clicks and typing, inspect network requests, and hand tabs back to the user, all without touching other tabs or stealing focus.
      1
      MIT

    • Safari MCP Server

      lxman
      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

    • periscope

      oskar-szulc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a real Safari WebKit browser on macOS: navigate pages, click and fill forms, read content as markdown, and extract page records as structured JSON. Named sessions persist logins between commands, and CAPTCHA or bot-check pages are detected and reported.
      MIT

    • mcp-desktop

      mocha06
      F
      license
      Not graded
      quality
      D
      maintenance
      macOS desktop automation enabling AI agents to screenshot, switch apps and tabs, click, type, and scroll. Offers two trust levels: read-only screenshot and full UI control.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools map cleanly to a single action (click, hover, type, navigate, screenshot, etc.), and the ref-based workflow from snapshot/find is explained. The only real soft spots are snapshot vs. get_text vs. find, which all return page content in different forms, and the catch-all browser_evaluate that can partially emulate several other tools.

    Naming Consistency4/5

    All 21 tools share a consistent browser_ prefix and snake_case, which makes the set easy to scan. Minor deviation: the pattern mixes verb-first (browser_get_text, browser_take_screenshot, browser_wait_for) with noun-only names (browser_tabs, browser_snapshot, browser_session, browser_doctor, browser_gif).

    Tool Count4/5

    21 tools is on the heavy side, but for full browser automation nearly every one covers a distinct capability (input, inspection, diagnostics, capture). The niche extras like browser_gif, browser_doctor and browser_resize are the only ones that feel optional rather than essential.

    Completeness4/5

    The surface covers navigation, history, tabs, element discovery, all major input actions, JS evaluation, console/network inspection, waiting and visual capture — a strong end-to-end automation loop. Notable gaps remain for common browser workflows: dialog (alert/confirm) handling, cookie/localStorage management, and file upload.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources