Skip to main content
Glama
anmolol117

AppleScript Automation MCP

by anmolol117
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AppleScript Automation MCP

No user-submitted related servers found.

    Related Servers

    • Mac-Commander

      martyfontaine
      F
      license
      Not graded
      quality
      B
      maintenance
      A minimal macOS GUI-automation MCP server providing tools to see app state, perform actions, manage apps, send notifications, and run AppleScripts with security boundaries.
      -

    • macos-mcp

      CursorTouch
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight MCP server that bridges AI agents and macOS, enabling automation of file navigation, application control, UI interaction, browser automation, and system operations.
      176
      MIT

    • automator-mcp

      VetCoders
      A
      license
      B
      quality
      D
      maintenance
      MCP server for macOS Automator that enables AI to control Mac computers by executing AppleScript/JXA, running automation workflows, and performing system-level tasks like sending emails and organizing files.
      6
      8 npm
      4
      MIT

    • macos-control-mcp

      vito1317
      A
      license
      B
      quality
      D
      maintenance
      MCP server that enables AI to fully control macOS — mouse, keyboard, terminal, screenshots, window management, UI element detection, and provides AI-optimized information reporting.
      36
      41 npm
      MIT

    • Apple-MCPs

      JonathanRReed
      A
      license
      C
      quality
      A
      maintenance
      Local macOS MCP servers for Mail, Calendar, Reminders, Notes, Contacts, Messages, Shortcuts, Files, Maps, and system tools. The unified Apple Tools server and individual app servers run over stdio with native macOS permissions; this is an MIT-licensed community project, unaffiliated with Apple.
      184
      12
      MIT
    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

    A3.5/5.0

    Scored across 39 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose covering system info, app management, media, communication, and utilities. There is no overlap that would confuse an agent; even closely related tools like mute and is_muted or set_volume and get_volume are easily distinguishable by their action vs. query nature.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., close_app, get_volume, send_imessage). There are no mixed conventions or abbreviations, making the naming predictable and easy to understand.

    Tool Count4/5

    With 39 tools, the server is extensive but still well-scoped for a general macOS automation tool. While slightly high, each tool addresses a distinct operation, and the count feels appropriate for the broad domain covered.

    Completeness3/5

    The tool set covers many common automation tasks (system info, apps, media, messaging, clipboard, reminders, shortcuts), but it lacks tools for file operations, calendar, browser control beyond opening URLs, and system preferences beyond volume/dark mode. These gaps limit its ability to handle some typical workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources