mcp-mac
Related Servers
Alternatives to mcp-mac
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI to dynamically discover and control native macOS applications (like Finder, Mail, Safari) through AppleScript/JXA automation without pre-built integrations.3MIT
- AlicenseAqualityBmaintenanceEnables macOS system automation, window management, and productivity tools for AI agents, including running AppleScripts, opening apps, retrieving browser tabs, taking screenshots, and controlling system settings.21MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI to control Apple Mac apps like Messages, Notes, Contacts, Mail, Reminders, Calendar, and Maps through natural language commands.106 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to automate macOS applications, manage files, control music, send messages, and more through AppleScript.14 npm1GPL 3.0
- AlicenseBqualityDmaintenanceEnables LLM applications to interact with macOS through AppleScript.3314 npm395MIT
- AlicenseAqualityDmaintenanceEnables AI agents to control macOS desktop apps via screenshots, mouse clicks, keyboard input, accessibility queries, and AppleScript.1114 npmMIT
TDQS
Scored across 24 tools
Every tool has a clearly distinct purpose with no ambiguity, as each is prefixed by its domain (e.g., calendar_, contacts_, finder_) and specifies a unique action (e.g., create_event, get_calendars, get_selection). The domains are well-separated, preventing misselection.
Tool names follow a highly consistent verb_noun pattern with domain prefixes (e.g., calendar_create_event, contacts_search_people). All use snake_case uniformly, and the naming structure is predictable across all 24 tools, making them easily readable and organized.
With 24 tools, the count is slightly high but reasonable for the broad scope of macOS automation covering multiple domains like calendar, contacts, mail, and notes. Each tool earns its place by addressing specific tasks, though it borders on heavy for a single server.
The tool surface provides strong CRUD/lifecycle coverage across domains, with create, get, and search operations for most resources. Minor gaps exist, such as no update/delete for calendar events or notes, but agents can work around these for core workflows.