Skip to main content
Glama
peakmojo

AppleScript MCP Server

by peakmojo

Related Servers

Alternatives to AppleScript MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Python server that enables interaction with macOS native applications (Contacts, Notes, Mail, Messages, Reminders, Calendar, and Maps) through AppleScript, featuring asynchronous operations and type-safe interfaces.
      16
      -
    • A
      license
      B
      quality
      C
      maintenance
      A comprehensive Model Context Protocol (MCP) server for Obsidian on macOS. It provides extensive tools for interacting with Obsidian vaults, notes, and application state through AppleScript, URI schemes, and direct file system access.
      42
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that provides a secure bridge for automating macOS applications like Notes, Calendar, and Mail through AppleScript. It uses template-based execution and policy-based allowlists to enable safe, structured interaction with system tools.
      MIT

    TDQS

    A3.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool 'applescript_execute' has a clear and distinct purpose, covering all AppleScript-related operations without any competing alternatives.

    Naming Consistency5/5

    The naming is trivially consistent as there is only one tool, 'applescript_execute', which follows a clear verb_noun pattern. No inconsistencies can exist in a single-tool set, so it meets the highest standard for naming predictability.

    Tool Count2/5

    A single tool for a server that interacts with multiple Mac applications and system features feels too thin and under-scoped. The tool count of 1 is borderline for any non-trivial domain, as it forces all operations through a single interface, which may limit clarity and efficiency for agents.

    Completeness3/5

    The tool surface is notably incomplete for the domain of Mac application and system interaction. While 'applescript_execute' can handle many tasks via scripting, there are obvious gaps in structured operations like dedicated CRUD for specific resources (e.g., notes, contacts), which could lead to agent inefficiencies or failures in complex workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive