Shortcuts

Created By
artemnovichkova year ago
Overview

what is Shortcuts MCP Server?

Shortcuts MCP Server is a Model Context Protocol (MCP) server that provides access to Apple Shortcuts functionality, allowing AI assistants to list, view, and run shortcuts through the MCP interface.

how to use Shortcuts MCP Server?

To use the Shortcuts MCP Server, clone the repository from GitHub, build the project using Swift, and configure it in your MCP-enabled application like Cursor or Claude Desktop.

key features of Shortcuts MCP Server?

  • Access to Apple Shortcuts functionality via MCP interface.
  • Compatibility with various MCP-enabled applications.
  • Ability to run, list, and view shortcuts.

use cases of Shortcuts MCP Server?

  1. Integrating Apple Shortcuts with AI assistants.
  2. Automating tasks using shortcuts through voice commands.
  3. Enhancing productivity by managing shortcuts programmatically.

FAQ from Shortcuts MCP Server?

  • What is the purpose of the Shortcuts MCP Server?

It allows AI applications to interact with Apple Shortcuts, enabling automation and task management.

  • Is it compatible with all MCP-enabled applications?

Yes, it is designed to work with various MCP-enabled applications like Cursor and Claude Desktop.

  • How do I install the Shortcuts MCP Server?

You can install it by cloning the repository and building it using Swift.

Server Config

{
  "mcpServers": {
    "shortcuts-mcp-server": {
      "type": "stdio",
      "command": "/absolute/path/to/shortcuts-mcp-server/.build/arm64-apple-macosx/debug/shortcuts-mcp-server"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
artemnovichkov
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

34 minutes ago