list_shortcuts
List all available shortcuts
Run any Shortcuts automation you have already built by name, and pass it an input from the conversation.
LABSCO SUMMARY
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.
A two-tool bridge to the Shortcuts app: list what is on the machine, run one of them with an input value.
The Shortcuts app on the machine, with the automations you want to run already saved there. Apache-2.0 licensed.
One command — npx -y mcp-server-apple-shortcuts
USE CASES
See what is on the machine, then run the one you want by name — the work of building it stays where it was done.
A shortcut that takes input becomes a parameterised action: the text, path or number under discussion goes in as the input and the automation does the rest.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list_shortcutsList all available shortcuts
run_shortcutRun a Shortcuts automation by name
BEFORE YOU INSTALL
2 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"mcp-server-apple-shortcuts": {
"command": "npx",
"args": [
"-y",
"mcp-server-apple-shortcuts"
]
}
}
}npx -y mcp-server-apple-shortcuts