Summary
Whatever you already automated in Shortcuts becomes callable by name.
The surface is two tools, and that is the point: the capability is whatever you have already built, so anything Shortcuts can drive is reachable without writing an integration per app. Nothing here inspects, creates or edits a shortcut, so authoring stays in the Shortcuts app and this side stays a trigger. The input parameter is what makes it more than a button — a value from the conversation can be handed to the automation as it runs.
What it is
A two-tool bridge to the Shortcuts app: list what is on the machine, run one of them with an input value.
What you get
- A list of the shortcuts available on the machine, by name
- Execution of a named shortcut with an input value passed into it
Requirements
The Shortcuts app on the machine, with the automations you want to run already saved there. Apache-2.0 licensed.
Setup effort
One command — npx -y mcp-server-apple-shortcuts