Skip to main content
Glama
Apple Shortcuts Server

Apple Shortcuts Server

by recursechat

Apple Shortcuts MCP Server 🤖

A Model Context Protocol (MCP) server that lets AI assistants like Claude control Apple Shortcuts automations. This enables AI models to trigger shortcuts and automate tasks on macOS in a safe and controlled way.

What is MCP? 🤔

The Model Context Protocol (MCP) is a system that lets AI apps, like Claude Desktop, connect to external tools and data sources. It gives a clear and safe way for AI assistants to work with local services and APIs while keeping the user in control.

Related MCP server: mcp-netbird

What does this server do? 🚀

The Apple Shortcuts MCP server:

  • Enables AI assistants to list available shortcuts

  • Allows running shortcuts by name with optional input parameters

  • Provides a simple interface for automation control

Prerequisites 📋

Before you begin, ensure you have:

Configuration to use Apple Shortcuts Server ⚙️

Here's the Claude Desktop configuration to use the Apple Shortcuts server:

{
  "mcpServers": {
    "apple-shortcuts": {
      "command": "npx",
      "args": ["-y", "mcp-server-apple-shortcuts"]
    }
  }
}

Build Apple Shortcuts Server and run locally 🛠️

  1. Clone this repository:

git clone git@github.com:recursechat/mcp-server-apple-shortcuts.git
  1. Install dependencies:

npm install
  1. Build project

npm run build

Here's the Claude Desktop configuration to use the Apple Shortcuts server with a local build:

{
  "mcpServers": {
    "apple-shortcuts": {
      "command": "npx",
      "args": ["/path/to/mcp-server-apple-shortcuts/build/index.js"],
    }
  }
}

Usage 🎯

You can ask Claude "list shortcuts" or run a specific shortcut with the shortcut name, for example "get word of the day" or "play a song".

License ⚖️

Apache-2.0

Available Tools

2 tools
list_shortcutsB

List all available shortcuts

Inputs: no named parameters.

run_shortcutC

Run a Shortcuts automation by name

Inputs: name (required), input.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists available shortcuts, while the other executes a specific shortcut by name. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (list_shortcuts, run_shortcut), using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count2/5

    With only two tools, the server feels thin for its apparent domain of managing and running Apple Shortcuts. While the tools cover basic listing and execution, the scope suggests potential gaps, such as creating, editing, or deleting shortcuts, making the count seem insufficient for comprehensive automation workflows.

    Completeness2/5

    The tool surface is significantly incomplete for a shortcuts management server. It lacks essential operations like creating, updating, or deleting shortcuts, which are core to lifecycle management. This will likely cause agent failures when tasks require modification or setup of shortcuts beyond just listing and running existing ones.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers