A
licenseNot graded
qualityB
maintenanceEnables AI agents like Claude Code and Codex to invoke selected Mac app actions (e.g., Reminders, Calendar, Notes) as MCP tools, wrapped as Shortcuts and verified via readback, using only public APIs.
7
MIT
shortcut-forge
by Hyunki6040
Related Servers
Alternatives to shortcut-forge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that lets ChatGPT list, search, and run your Apple Shortcuts on your own Mac through a local agent and stateless relay.MIT
- AlicenseNot gradedqualityBmaintenanceEnables generation of Apple Shortcuts through schema-validated MCP tools for catalog navigation, control-flow construction, validation, and signing.MIT
- AlicenseAqualityDmaintenanceConnects LLMs to your macOS Shortcuts library, enabling interactive workflows, discovery, and management through AppleScript and CLI integration.311MIT
- 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.1MIT
- 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.157 npmMIT
TDQS
A3.5/5.0
Scored across 10 tools
Disambiguation4/5
Each tool targets a distinct stage of the shortcut authoring pipeline (build, template, inspect, sign, lint, reference, library, submit, publish, prompt), so selection is mostly obvious. The only real overlap is shortcut_publish, which internally performs build+sign and could be confused with shortcut_build/shortcut_sign, though its manifest/update purpose is spelled out.
Naming Consistency5/5
Every tool uses the same snake_case `shortcut_` prefix with a clear verb or noun-suffix (build, inspect, sign, lint, publish, submit). The one prepositional name, shortcut_from_template, still fits the pattern and reads naturally.
Tool Count5/5
Ten tools is squarely in the well-scoped range, and each one covers a genuinely different step (authoring, templating, validation, signing, distribution, docs, discovery). Nothing appears redundant or padded.
Completeness4/5
The authoring-to-publishing lifecycle is well covered: build, template, inspect, lint, sign, publish, submit, plus docs and a library. Minor gaps remain — there is no tool to decompile an existing .shortcut back into an editable spec, and no test/run simulation beyond linting, which agents must work around manually.
Maintenance
ActivityMaintained
ResponsivenessOutdated data