Siri Shortcuts MCP Server

Created By
dvcrna year ago
MCP for calling Siri Shorcuts from LLMs
Overview

What is Siri Shortcuts MCP Server?

The Siri Shortcuts MCP Server provides access to Siri shortcuts functionality via the Model Context Protocol (MCP), allowing users to list, open, and run shortcuts from the macOS Shortcuts app.

How to use Siri Shortcuts MCP Server?

To use the MCP server, integrate it into your Claude configuration by adding the provided command and arguments. This allows you to interact with Siri shortcuts through your application.

Key features of Siri Shortcuts MCP Server?

  • Exposes all shortcuts available in the Shortcuts app.
  • Lists all available shortcuts.
  • Opens shortcuts directly in the Shortcuts app.
  • Runs shortcuts with optional input parameters.
  • Dynamically generates tools for each available shortcut.

Use cases of Siri Shortcuts MCP Server?

  1. Automating tasks on macOS using Siri shortcuts.
  2. Integrating Siri shortcuts into applications for enhanced functionality.
  3. Running complex workflows through voice commands or automated scripts.

FAQ from Siri Shortcuts MCP Server?

  • Can I access all my Siri shortcuts?

Yes! The MCP server exposes all shortcuts available in the Shortcuts app.

  • Is there any input required to run a shortcut?

Input is optional; you can run shortcuts without any parameters if they do not require them.

  • How do I integrate the MCP server?

You can integrate it by adding the specified command to your Claude configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dvcrn
Star
133
Language
TypeScript
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