About Apple Shortcuts
Apple Shortcuts is an MCP server for discovering, inspecting, and running Apple Shortcuts on macOS. It is for users who want agents to invoke existing automations, with structured input and output handling plus tool discovery and state checks.
Key features
- 01List shortcuts and folders
- 02Inspect shortcut details
- 03Run shortcuts with input and output handling
- 04Provide tool discovery helpers
- 05Check health and catalog state
Use cases
- 01Trigger existing Apple Shortcuts through an agent
- 02Run local automation without shell orchestration
- 03Confirm a shortcut before executing it
MCP support
The MCP server exposes shortcut listing, inspection, and execution tools to clients, along with related resources and execution prompts.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
11Saved tool list · updated 1d ago
This tool takes no parameters.
Details
From the project READMEApple Shortcuts MCP
MCP server for Apple Shortcuts on macOS.
Provides access to shortcuts for discovery, inspection, and execution. Run shortcuts with structured input and output handling.
When to use
- Triggering existing Apple Shortcuts from agents
- Local automation without shell orchestration
- Smaller scope than the all-in-one server
What It Does
- List shortcuts and folders
- Inspect shortcut details
- Run shortcuts with input/output handling
- Tool discovery helpers
search_toolsandget_tool_infofor context-constrained clients - Shortcut resources and execution prompts
- Health and state checks:
shortcuts_health,shortcuts_permission_guide,shortcuts_refresh_state
Install On This Mac
Quick start (uvx, from PyPI)
With uv installed:
uvx apple-shortcuts-mcp
No clone, no venv management.
From a clone
git clone https://github.com/JonathanRReed/Apple-MCPs.git
cd Apple-MCPs
uv sync --all-packages
This builds one workspace environment with every server's entry point in .venv/bin (for example .venv/bin/apple-shortcuts-mcp). You can also point an MCP client at AppleShortcuts-MCP/start.sh, which prefers uv run and falls back to a plain venv bootstrap (Python 3.11+ required).
Install In AI Agents
Generic MCP client config
{
"mcpServers": {
"apple-shortcuts": {
"command": "uvx",
"args": ["apple-shortcuts-mcp"],
"env": {
"APPLE_SHORTCUTS_MCP_SAFETY_MODE": "full_access"
}
}
}
}
Running from a clone instead? Use /path/to/Apple-MCPs/AppleShortcuts-MCP/start.sh as the command with empty args.
Claude Code example
claude mcp add --transport stdio --scope user apple-shortcuts -- uvx apple-shortcuts-mcp
--scope user makes the server available in every project. To share it with one repository through its .mcp.json instead, use --scope project.
Transport
stdio is the default and recommended transport. Set APPLE_SHORTCUTS_MCP_TRANSPORT=streamable-http (with optional APPLE_SHORTCUTS_MCP_HOST and APPLE_SHORTCUTS_MCP_PORT) to serve Streamable HTTP instead.
macOS Requirements
- the built-in
shortcutsCLI must be available
Launch Checklist
- Add
uvx apple-shortcuts-mcp(or a clone'sAppleShortcuts-MCP/start.sh) to your MCP client - Reload or reconnect the client so the Shortcuts tool surface is loaded into context
- Call
shortcuts_healthfirst - If the CLI is unavailable, call
shortcuts_permission_guide - After changing the Shortcuts catalog, call
shortcuts_refresh_state
Prompting Notes
tools/listreturns the full Shortcuts tool surface. Context-constrained clients can usesearch_toolsfirst, thenget_tool_infofor the Shortcuts tool they need.- If the user asks for a shortcut vaguely, list available shortcuts first.
- Run a shortcut only after confirming which shortcut to run.
Related
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.