Summary
Whatever you have already automated in Shortcuts becomes one call from the client.
run_shortcut takes a name or a UUID with optional input and output, so an existing shortcut — a home automation, a file conversion, a capture into notes — is reachable without being rebuilt anywhere else. The server does not author shortcuts: open_shortcut hands that job back to the Shortcuts app. What is reachable is exactly what is installed on that machine, which is what the listing enumerates.
What it is
A server over the Shortcuts app on the host machine: the installed shortcuts listed, run, or opened for editing.
What you get
- Every installed shortcut listed by name
- A shortcut run by name or by UUID, with optional input passed in and output returned
- A shortcut opened in the Shortcuts app when what it needs is editing rather than running
Requirements
A machine with the Shortcuts app, holding the shortcuts you want to reach. Two environment variables are read, GENERATE_SHORTCUT_TOOLS and INJECT_SHORTCUT_LIST. GPL-3.0.
Setup effort
One command — npx mcp-server-siri-shortcuts