Apple Shortcuts MCP Server 🤖

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Apple Shortcuts MCP Server?

The Apple Shortcuts MCP Server is a Model Context Protocol (MCP) server that allows AI assistants like Claude to control Apple Shortcuts automations, enabling them to trigger shortcuts and automate tasks on macOS safely and effectively.

How to use Apple Shortcuts MCP Server?

To use the server, ensure you have Node.js and Claude Desktop installed on macOS. Configure the server in Claude Desktop and use commands like 'list shortcuts' or 'run [shortcut name]' to interact with your shortcuts.

Key features of 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.

Use cases of Apple Shortcuts MCP Server?

  1. Automating daily tasks on macOS using voice commands.
  2. Integrating AI capabilities with existing Apple Shortcuts for enhanced functionality.
  3. Streamlining workflows by triggering multiple shortcuts in sequence.

FAQ from Apple Shortcuts MCP Server?

  • What are the prerequisites to use the server?

You need Node.js (v18 or higher), Claude Desktop, and macOS with the Shortcuts app configured.

  • Can I run the server locally?

Yes! You can clone the repository, install dependencies, and run the server locally.

  • What commands can I use with the server?

You can use commands like 'list shortcuts' or run specific shortcuts by name.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago