Siri Shortcuts MCP Server for macOS
Control Siri Shortcuts on macOS with an MCP server, exposing all Shortcuts as MCP tools for easy automation and remote triggering.
npx mcp-server-siri-shortcutsOverview
This MCP server exposes every macOS Shortcut as an MCP (Model Context Protocol) tool so you can discover, inspect, and trigger Shortcuts programmatically. It runs locally on macOS and translates MCP tool invocations into calls to the Shortcuts runtime on the host. The result is a simple bridge that lets automation systems, LLM agents, or remote controllers treat Shortcuts like first-class tools.
Using an MCP surface means your LLM-driven flows or automation orchestrators can list available Shortcuts, read their argument schemas (when available), and execute them with structured inputs — all over a minimal HTTP/JSON API. That makes it easy to integrate existing Shortcuts into larger automation pipelines or to expose Shortcuts to remote trigger systems while keeping execution on the macOS device.
Features
- Automatically expose every macOS Shortcut as an MCP tool
- List tools with names, identifiers and input metadata
- Invoke a Shortcut by name or ID with structured inputs
- Return Shortcut output and execution status to the caller
- Token-based authentication and optional TLS
- Lightweight local server designed for macOS Shortcuts CLI/backing runtime
- Simple JSON endpoints suitable for MCP client integrations and LLM agents
Installation / Configuration
Prerequisites:
- macOS with Shortcuts available (macOS Ventura or later recommended)
- Git and a build/runtime toolchain for the project (see repository for language-specific build steps)
Clone and run (example):
# Clone the repository
# Build or run per the project instructions; many implementations provide a single executable
# Example: if the project builds to a binary `mcp-siri-shortcuts`
Configuration via environment variables (example):
# optional
# optional
Example JSON configuration file (example/config.json):
Notes on macOS permissions:
- The server invokes the Shortcuts runtime (often via the
shortcutscommand-line tool). When prompted, allow the server to control the Shortcuts app and any other apps the Shortcuts use. - Grant Accessibility or Automation permissions if macOS requests them for the server binary or terminal app you use to run it.
Available Tools / Resources
The server maps each Shortcut to an MCP tool. Each tool typically exposes:
- id: internal identifier (stable across server restarts unless you change the Shortcut)
- name: human-readable name (the Shortcut’s name)
- description: if available from Shortcut metadata
- inputs: list of named parameters (type information may vary)
- run endpoint: server-side entry point to execute this Shortcut
You can list tools:
Sample response (abridged):
Invoke a tool:
Example response: