A
licenseNot graded
qualityC
maintenanceMCP server that lets ChatGPT list, search, and run your Apple Shortcuts on your own Mac through a local agent and stateless relay.
MIT
Askew
by Dominic-DK
Related Servers
Alternatives to Askew
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP Server Integration with Apple Shortcuts22393 npm352Apache 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 Claude, Codex, ChatGPT and other MCP clients to turn plain-language automation requests into real, lint-checked iOS Shortcuts (.shortcut) files that are signed automatically on a Mac and importable on iPhone. It also offers a browsable shortcut library, templates, inspection and publishing tools so those automations can be reviewed, versioned and shared.44 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables generation of Apple Shortcuts through schema-validated MCP tools for catalog navigation, control-flow construction, validation, and signing.MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLMs to list, open, and run shortcuts from the macOS Shortcuts app through MCP, including optional text or file input and dynamically generated tools for available shortcuts.88 npmMIT
TDQS
A4.4/5.0
Scored across 9 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues