mac-control-mcp MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

postinstall: node scripts/install.js

  const child = spawn(BINARY_PATH, args, { stdio: 'inherit' });

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        let process = Process()

    exec(compile(ast.Module(body=[function], type_ignores=[]), 'session.py', 'exec'), namespace)

    completed = subprocess.run(argv, env=env, text=True, capture_output=True, timeout=900, check=True)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mac-control-mcp -- npx -y mac-control-mcp

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

[mcp_servers.mac-control-mcp]
command = "npx"
args = ["-y", "mac-control-mcp"]

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

{
  "servers": {
    "mac-control-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mac-control-mcp"
      ]
    }
  }
}