MacPilot CLI

Created By
huhu415a year ago
MacPilot CLI is a mcp server, It provides a collection of system tools that allow AI assistants to perform various operations on macOS systems.
Overview

What is MacPilot CLI?

MacPilot CLI is an open-source tool that enables interaction with macOS through the Model Control Protocol (MCP). It allows AI assistants to perform various operations on macOS systems, such as mouse control, screenshots, text pasting, and application launching.

How to use MacPilot CLI?

To use MacPilot CLI, you need a Mac computer with Apple Silicon running macOS 14.0 (Sonoma) or later. Download the binary file from the Releases section on GitHub, configure your MCP-compatible application, and grant the necessary permissions.

Key features of MacPilot CLI?

  • Control mouse movements and clicks
  • Take screenshots of the entire screen
  • Paste text from the clipboard
  • Launch applications and execute shell commands
  • Retrieve information about installed applications and windows

Use cases of MacPilot CLI?

  1. Automating repetitive tasks on macOS using AI assistants.
  2. Enhancing accessibility features for users with disabilities.
  3. Integrating with AI models to perform complex operations on macOS.

FAQ from MacPilot CLI?

  • What macOS versions are supported?

MacPilot CLI supports macOS 14.0 (Sonoma) and later.

  • Is MacPilot CLI free to use?

Yes! MacPilot CLI is an open-source tool and is free to use.

  • What permissions are required to use MacPilot CLI?

You need to grant screen recording and accessibility permissions to the application using MacPilot CLI.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
huhu415
Star
6
Language
Swift
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.

32 minutes ago