Macbeth MCP Server

Most developer tooling work still happens through a UI a human drives. Macbeth MCP server moves it into the conversation instead. Open-source Computer Use for macOS. See and operate Mac applications through MCP or TypeScript, including native and Electron interfaces.

The short version

• Use your own agent. — Macbeth is a control layer, not a model or agent runtime
• Structured when possible. — Query roles, labels, values, enabled state, hierarchy, and stable handles instead of relying only on coordinates
• Visual when necessary. — Fall back to window capture and OCR when accessibility metadata is thin
• Application-aware. — Versioned skills preserve workflows, shortcuts, and known failure modes
• Scriptable. — Use the same primitives interactively over MCP or directly from TypeScript

What it needs from you

• macOS 14 (Sonoma) or later - Node.js 20+ - Swift 6.0+ only when building the daemon from source

Getting it running

macbeth on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.