Skip to main content
Glama
FradSer

mcp-server-osascript

by FradSer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-server-osascript

No user-submitted related servers found.

    Related Servers

    • DesktopBridge

      jameymcelveen
      A
      license
      A
      quality
      B
      maintenance
      Enables local macOS automation via the Model Context Protocol, allowing file operations, system monitoring, shell commands, clipboard access, and screenshots with configurable security restrictions.
      14
      MIT

    • MCP AppleScript

      pietz
      A
      license
      A
      quality
      C
      maintenance
      Enables Large Language Models to automate macOS applications and execute AppleScript commands through natural language. It features built-in security protections including application allowlists and dangerous pattern detection to prevent unauthorized or risky system operations.
      2
      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,313 npm
      8
      MIT

    • 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,313 npm
      884
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: execute_osascript for running scripts, get_security_profiles for listing profiles, and set_security_profile for changing the default. There is no functional overlap between them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (execute_osascript, get_security_profiles, set_security_profile), making the naming predictable and easy to learn.

    Tool Count5/5

    Three tools is an appropriate size for this focused server, covering the core execution capability and necessary security configuration without unnecessary bloat.

    Completeness5/5

    The server provides complete lifecycle coverage for its domain: executing scripts (with dry-run and security profiles), reading available security profiles, and updating the default profile. There are no obvious missing operations for this purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources