macOS Automator MCP Server

Provides comprehensive access to a curated knowledge base of AppleScript/JXA tips and runnable scripts for macOS automation. This tool is essential for discovery and should be the FIRST CHOICE when aiming to automate macOS tasks, especially those involving common applications or system functions, before attempting to write scripts from scratch. It helps identify pre-built, tested solutions.

Primary Use Cases & Parameters:

• Discovering Solutions (Use searchTerm):
  • Parameter: searchTerm (string, optional).
  • Functionality: Performs a fuzzy search across all tip titles, descriptions, keywords, script content, and IDs. Ideal for natural language queries like "how to..." (e.g., searchTerm: "how do I get the current Safari URL and title?") or keyword-based searches (e.g., searchTerm: "Finder copy file to new location"). This is the most common way to find relevant tips.
  • Output: Returns a list of matching tips in Markdown format.
• Listing All Categories (Use listCategories):
  • Parameter: listCategories (boolean, optional, default: false).
  • Functionality: If true, this will return a list of all available script categories (e.g., "safari", "finder_operations", "system_interaction") along with their descriptions and the number of tips in each. This overrides all other parameters.
  • Output: A Markdown list of categories.
• Browsing a Specific Category (Use category):
  • Parameter: category (string, optional).
  • Functionality: Retrieves all tips belonging to the specified category ID. Useful if you know the general area of automation you're interested in.
  • Output: All tips within that category, formatted in Markdown.
• Forcing a Knowledge Base Reload (Use refreshDatabase):
  • Parameter: refreshDatabase (boolean, optional, default: false).
  • Functionality: If true, forces the server to reload the entire knowledge base from disk before processing the request. Primarily useful during development if knowledge base files are being actively modified and you need to ensure the latest versions are reflected without a server restart.

Output Details: The tool returns a single Markdown formatted string. Each tip in the output typically includes:

• Title: A human-readable title for the tip.
• Description: A brief explanation of what the script does.
• Language: applescript or javascript.
• Script: The actual code snippet.
• Runnable ID: A unique identifier (e.g., safari_get_front_tab_url). This ID is critical as it can be directly used as the kbScriptId parameter in the execute_script tool for immediate execution.
• Arguments Prompt: If the script is designed to take inputs when run by ID, this field describes what arguments or inputData are expected by execute_script.
• Keywords: Relevant search terms.
• Notes: Additional context or important considerations.

Workflow Example:

1. User asks: "How do I create a new note in the Notes app with a specific title?"
2. Agent calls get_scripting_tips with searchTerm: "create new note in Notes app with title".
3. Agent reviews the output. If a tip like notes_create_new_note_with_title with a Runnable ID and an argumentsPrompt for noteTitle and noteBody is found:
4. Agent then calls execute_script with kbScriptId: "notes_create_new_note_with_title" and appropriate inputData.