MacMCPControl

MCP运维云端

提供方 michaellatman

运维云端 stdio · 本地进程 OAuth 授权 社区 / 第三方 Zed

A macOS menubar app that turns a Mac into a local, user-approved MCP control server, exposing MCP over HTTP with OAuth approval and native macOS API actions.

一句话选型结论

按资料字段整理

MacMCPControl 属于运维云端类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Local Deployment MCP Server OAuth Authentication Swift macOS Automation Remote Control Shell Commands Screenshots Keyboard/Mouse Control ngrok Tunnel

支持客户端

Zed

适用场景

Local DeploymentMCP ServerOAuth Authentication

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Zed,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Zed 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MacMCPControl当前 未标注 stdio · 本地进程 本地部署 无 2026-08-29
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方michaellatman上游标注的维护方 michaellatman
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-08-29上游最后核验时间

详细介绍

7.3 KB
来自项目仓库与上游目录的原文,未做删改

Mac MCP Control

Mac MCP Control is a macOS menubar app that turns a Mac into a local, user‑approved control server. It exposes MCP over HTTP, gates access through in‑app OAuth approval, and executes actions through native macOS APIs. It is built for real workflows: local automation, remote control via ngrok when needed, and clear session management.

> Disclaimer: Remote control of your Mac carries inherent risks. By using this software, you accept full responsibility for actions taken with it. The author is not liable for damages, data loss, or security incidents.

What It Does

  • Hosts an MCP server on your Mac (default port 7519).
  • Uses OAuth 2.0 + S256 PKCE; approvals happen only inside the app.
  • Executes actions: mouse, keyboard, screenshots, scroll, and shell commands.
  • Manages sessions with revocation and live activity tracking.
  • Optionally tunnels public access through ngrok.

Requirements

  • macOS 14.0+
  • Xcode Command Line Tools (for building from source)

Install

Releases

Download the latest build from the Releases page.

Build from Source```bash

git clone https://github.com/michaellatman/MacMCPControl.git
cd MacMCPControl
./scripts/build.sh
open MacMCPControl.app


## First Launch

You will be prompted for:
1. **Accessibility** (mouse/keyboard control)
2. **Screen Recording** (screenshots)
3. **Terms Acceptance**

After onboarding, the server starts automatically.

## Configuration

Settings are accessible from the menubar (Cmd+,):

- **Device Name** — label for this Mac
- **MCP Port** — default 7519
- **Enable ngrok tunnel** — public URL when needed
- **Ngrok Token** — optional auth token

Sessions tab shows active authorizations. You can rename, revoke selected, or revoke all.

## MCP Endpoints

- Local: `http://localhost:7519/mcp`
- Public (ngrok): `https://.ngrok.app/mcp`
- Discovery:
  - `/.well-known/oauth-authorization-server`
  - `/.well-known/oauth-protected-resource`

## Security Model

- OAuth approvals are in‑app only; the browser cannot grant access.
- Access tokens expire after one hour; refresh tokens expire after 30 days.
- Revocation blocks new actions; “revoke all” also rotates the signing key and clears pending approvals.
- OAuth signing key, refresh tokens, and revoked clients are stored in macOS Keychain.
- If you enable ngrok, revoke access and stop the tunnel when done. The URL is not an authentication secret.

## Architecture```mermaid
flowchart LR
  Client[OAuth Client] -->|/oauth/authorize| MCP[MCP Server]
  MCP -->|/oauth/approve| Browser[Approval Page]
  Browser -->|poll /oauth/pending| MCP
  MCP -->|pending auth| App[Mac MCP Control App]
  App -->|approve/deny| MCP
  MCP -->|redirect with code| Browser
  Browser -->|/oauth/token| MCP
  MCP -->|Bearer tokens| Client
  Client -->|/mcp tools| MCP
  MCP -->|actions| Mac[macOS APIs]
``````mermaid
flowchart TB
  App[Mac MCP Control] -->|Keychain write| Keychain[(Keychain)]
  Keychain -->|oauth_signing_key| Key[Signing Key]
  Keychain -->|refresh_tokens| Refresh[Refresh Tokens]
  Keychain -->|revoked_clients| Revoked[Revoked Clients]
  MCP[MCP Server] -->|validate bearer| Key
  MCP -->|refresh exchange| Refresh
  MCP -->|revocation check| Revoked

License

See LICENSE.

Security changes and client migration

After this update, reconnect existing clients. Tokens from older releases do not contain an approval identifier and are rejected.

The server listens only on 127.0.0.1. Enable ngrok for remote access; direct LAN access is not supported. Incoming host and browser origin headers must match localhost or the active HTTPS tunnel. OAuth metadata uses the known tunnel URL, not caller-supplied forwarded headers.

Clients must register their exact callback URLs through /oauth/register before authorization. Supported callbacks are HTTPS, loopback HTTP, and app-specific reverse-DNS native schemes. Fragments and embedded credentials are rejected. Authorization requires S256 PKCE and the mcp:tools scope. Arbitrary client IDs, plain PKCE, and unregistered callbacks are not supported.

The MCP resource metadata and unauthenticated response advertise mcp:tools. A missing or empty authorization scope defaults to mcp:tools; other scopes are rejected. This also supports clients with a cached registration from before scope discovery was available. In-app approval is still required.

Each access token is bound to a live approval. Revoking a client invalidates its tokens and unredeemed codes. Reauthorizing does not revive its old tokens. Revoke all also cancels pending approvals. Revocation stops future requests and remaining actions in a batch; it cannot undo an action or stop a shell process that already started.

Shell commands are off by default. Enable “Allow shell commands” in Settings only when needed. This setting is not a sandbox: computer control can still open Terminal, operate signed-in apps, and access your data. Only approve clients you trust with your account. The app does not ask for approval for each action.

The patched HTTP transport limits bodies to 1 MiB, request lines to 8 KiB, headers to 32 KiB and 100 fields, and concurrent connections to 32. Socket reads and writes have a 10-second idle timeout. It rejects duplicate headers and transfer encoding rather than guessing message boundaries. Authorization prompts are limited to 10 per minute and 16 pending requests. Client registration is limited to 10 per minute and 256 stored clients. At capacity, the oldest registration with no live approval or pending request is replaced; that client must register again. These limits reduce resource exhaustion; they do not guarantee availability under attack.

Release notarization

GitHub releases require these repository secrets in addition to the existing signing certificate secrets:

  • APP_STORE_CONNECT_API_KEY_BASE64: base64-encoded App Store Connect API private key (.p8)
  • APP_STORE_CONNECT_KEY_ID: the API key ID
  • APP_STORE_CONNECT_ISSUER_ID: the API issuer ID

Create a Team API key with the Developer role on the team that owns the Developer ID certificate. Admin access is not needed. Add the values through GitHub repository settings or gh secret set; do not commit them or paste them into issue comments.

The release workflow builds through scripts/build-app.sh. scripts/notarize.sh signs nested executable code and the app with hardened runtime and a secure timestamp, submits the app to Apple, waits for acceptance, staples the ticket, and checks Gatekeeper. It then creates the public archives and repeats signature, ticket, and Gatekeeper checks on the extracted ZIP. Any failure prevents publication.

Local scripts/build.sh builds an ad-hoc-signed development app unless APPLE_SIGNING_IDENTITY is set. It does not notarize or publish. To test distribution, use a notarized archive downloaded through a browser on a Mac that has not approved the app before. Do not remove quarantine or disable Gatekeeper to validate a release.

Tests

Run swift test for OAuth, server, and HTTP parser regressions. Tests inject in-memory token storage and isolated preferences; they do not read or change your app's Keychain credentials. One test starts a temporary loopback-only listener. Run python3 -m unittest discover -s Tests/Release to check the notarization script's success and failure paths with fake command-line tools. These script tests do not submit software to Apple.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MacMCPControl 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MacMCPControl 怎么在 Zed 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MacMCPControl 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MacMCPControl 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

MacMCPControl 支持哪些客户端?

资料标注支持 Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MacMCPControl 能提供哪些能力?

资料显示能力标签包括 Local Deployment、MCP Server、OAuth Authentication、Swift、macOS Automation、Remote Control。具体工具清单以官方文档为准。

MacMCPControl 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

MacMCPControl 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-08-29。