🚀 Automation MCP

Created By
ashwwwina year ago
Control your Mac with detailed mouse, keyboard, screen, and window management capabilities.
Overview

What is Automation MCP?

Automation MCP is a Model Context Protocol (MCP) server that provides AI models with complete desktop automation capabilities on macOS, allowing AI assistants to control mouse, keyboard, and manage windows.

How to use Automation MCP?

To use Automation MCP, install the required dependencies, clone the repository, and start the server. You can also use the furi tool for easier setup.

Key features of Automation MCP?

  • Control mouse actions (click, move, scroll)
  • Send keyboard inputs and system shortcuts
  • Take screenshots and analyze screen content
  • Manage windows (focus, move, resize)
  • Interact with UI elements and analyze screen colors

Use cases of Automation MCP?

  1. Automating repetitive tasks on macOS
  2. Enhancing AI assistants with desktop control capabilities
  3. Creating custom automation scripts for various applications

FAQ from Automation MCP?

  • What permissions are required?

Accessibility and Screen Recording permissions must be granted for full functionality.

  • Is Automation MCP cross-platform?

While it is designed for macOS, it has components that support cross-platform functionality.

  • How do I troubleshoot permission errors?

Ensure that the necessary permissions are granted and that Xcode Command Line Tools are installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ashwwwin
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours 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.

a day ago