mac-control-mcp

mac-control-mcp runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/AdelElo13/mac-control-mcp/releases/download/v0.10.0/mac-control-mcp-v0.10.0.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.

mac-control-mcp runs locally from a Node.js package published to the npm registry: mac-control-mcp version 0.10.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y mac-control-mcp@0.10.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mac-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mac-control-mcp@0.10.0"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect