Askew
Related Servers
Alternatives to Askew
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that lets ChatGPT list, search, and run your Apple Shortcuts on your own Mac through a local agent and stateless relay.MIT
- AlicenseBqualityDmaintenanceAn MCP Server Integration with Apple Shortcuts22,752 npm350Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT or other remote MCP clients to create Apple Reminders and lists, Calendar events, and Notes on a Mac through an Apple Shortcut, with tunnel or self-hosted HTTPS/OAuth connectivity.MIT
- AlicenseNot gradedqualityBmaintenanceEnables generation of Apple Shortcuts through schema-validated MCP tools for catalog navigation, control-flow construction, validation, and signing.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to access Apple HealthKit workout data by receiving workout information from iOS Shortcuts and serving it through MCP protocol endpoints.-
- AlicenseCqualityAmaintenanceLocal macOS MCP servers for Mail, Calendar, Reminders, Notes, Contacts, Messages, Shortcuts, Files, Maps, and system tools. The unified Apple Tools server and individual app servers run over stdio with native macOS permissions; this is an MIT-licensed community project, unaffiliated with Apple.18421MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: running shortcuts, checking run status, listing routes, managing inbox items (list/wait/ack), sending notifications, and reading/writing shared variables. There is no overlap or ambiguity between tools.
All tools share the 'askew_' prefix, but the verb/noun order varies (e.g., 'askew_run' vs 'askew_inbox_list' vs 'askew_variables_get'). The pattern is readable and grouped by domain, but not perfectly uniform.
With 9 tools, the server is well-scoped for its purpose: discovering routes, executing them, polling results, handling phone-to-agent inbox messages, sending notifications, and managing shared variables. Each tool earns its place.
The tool surface covers the core lifecycle: route discovery, execution, status polling, inbox list/wait/ack, notification, and variable get/set. Minor gaps exist (e.g., no variable delete or run cancellation), but these are not essential for the main workflows.