AppleScript MCP Server (Dual access: python and node.js)

Created By
peakmojoa year ago
A macOS AppleScript MCP server
Overview

What is AppleScript MCP?

AppleScript MCP is a macOS server that allows users to run AppleScript code to interact with various Mac applications and data through a Model Context Protocol (MCP). It is designed to be simple and intuitive, requiring minimal setup.

How to use AppleScript MCP?

To use AppleScript MCP, you can run it using either Node.js or Python. For Node.js, you can execute the command via npx, and for Python, you need to install the necessary dependencies and run the server script.

Key features of AppleScript MCP?

  • Execute AppleScript commands to access Mac applications like Notes, Calendar, Contacts, and Messages.
  • Search for files using Spotlight or Finder.
  • Read and write file contents, and execute shell commands.

Use cases of AppleScript MCP?

  1. Creating reminders and calendar events.
  2. Managing notes and files on your Mac.
  3. Accessing system information like battery percentage and free disk space.
  4. Automating tasks such as taking screenshots or playing music.

FAQ from AppleScript MCP?

  • What programming languages does AppleScript MCP support?

AppleScript MCP can be accessed using both Node.js and Python.

  • Is there a license for AppleScript MCP?

Yes, AppleScript MCP is licensed under the MIT License.

  • How complex is the setup process?

The setup process is designed to be straightforward, with minimal configuration required.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
peakmojo
Star
4
Language
Python
License
MIT 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.

5 hours ago