Skip to main content
Glama
schmitzjimmy1-star

macos-automator-mcp

by schmitzjimmy1-star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to macos-automator-mcp

No user-submitted related servers found.

    Related Servers

    • macOS Automator MCP Server

      steipete
      A
      license
      A
      quality
      F
      maintenance
      Provides a Model Context Protocol server for executing AppleScript and JavaScript for Automation scripts on macOS, featuring a knowledge base of pre-defined scripts and supporting automation of macOS applications and system functions.
      2
      1,639 npm
      885
      MIT

    • AppleScript MCP

      Hassanali4
      A
      license
      A
      quality
      C
      maintenance
      Enables full control of macOS by executing AppleScript commands through an MCP server, allowing automation of tasks, application control, and system management.
      1
      167 npm
      15
      MIT

    • macOS Automator MCP Server

      SuperCrazyKaizen
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables execution of AppleScript and JavaScript for Automation scripts on macOS, allowing programmatic control of applications and system functions through a rich knowledge base of pre-defined scripts.
      2
      1,639 npm
      8
      MIT

    • osascript MCP Server

      Akira-Papa
      F
      license
      A
      quality
      D
      maintenance
      Enables the execution of AppleScript and JavaScript for Automation (JXA) on macOS to control applications, system events, and shell commands. It provides native automation capabilities with a security layer that permits most operations while specifically blocking file deletion commands.
      1
      6
      -
    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

    A4.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one discovers automation solutions and the other executes scripts. There is no overlap or ambiguity in their roles.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern in snake_case: 'execute_script' and 'get_scripting_tips'. The naming is predictable and readable.

    Tool Count4/5

    While only two tools exist, each serves an essential role in the discovery-execution workflow. The count is slightly below the typical range but is reasonable for the server's focused purpose.

    Completeness5/5

    The combination of a knowledge base for discovery and a general-purpose execution tool covers the full lifecycle of macOS automation. Arbitrary AppleScript/JXA can be executed, so there are no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources