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 Shortcuts21,078 npm348Apache 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.18415MIT
TDQS
Scored across 9 tools
Each tool targets a distinct concern: notification, inbox lifecycle (list/wait/ack), shared variables (get/set), and shortcut execution (run/get_run/list_routes). Overlapping tools like inbox_list and inbox_wait have clearly differentiated roles (fetch existing vs. block for new).
All tools share the askew_ prefix and use snake_case, which is consistent. Some ordering variation exists (inbox_list is noun-verb while list_routes is verb-noun, and notify/run are verb-only), but the pattern remains readable and predictable.
Nine tools is well-scoped for a mobile-bridge server. Each tool covers a necessary action (notify, handle inbox, share variables, execute shortcuts) without redundant or filler tools.
The tool surface covers the full lifecycle for each capability: inbox items can be fetched, waited on, and acknowledged; variables can be read and written; shortcut runs can be started, polled, and discovered via route listing. No critical dead ends are evident.