# ACMS [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/gattjoe/ACMS  
**GitHub Stars:** 3  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/acms

## Description
Apple Container MCP Server (ACMS) provides access to Apple's container CLI tool on macOS

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "acms": {
    "command": "uvx",
    "args": ["acms"]
  }
}
```

## Documentation

## What ACMS MCP server does

The ACMS MCP server provides an MCP interface to Apple's container CLI on macOS. It is intended for AI clients that need to work with Apple's container tooling through programmatic requests rather than relying on manually entered shell commands. The underlying project is associated with Apple's Containerization package and Container CLI efforts.

ACMS can run on the same Mac as the MCP client or be reached through HTTP/S from another system. The README gives an example in which a user asks an AI client to create an Ubuntu x64 container. The specific container action remains handled by Apple's CLI and its installed services.

## How it works

Apple container services must be running before the MCP server can perform container-related work. Start those services with `container system start`, then launch ACMS as a Python application. The server can bind to a selected host and port; the example uses port 8765 and the loopback address `127.0.0.1`.

For remote access, ACMS exposes an HTTP MCP endpoint. The documented client configuration points to `http://localhost:8765/mcp` and uses the HTTP transport. This makes the server suitable for a client on the same machine or, with the relevant network setup, a client connecting to a remote Mac.

## Setup and configuration

The ACMS MCP server requires an Apple Silicon Mac. The documented target is macOS 26 or newer, while Sequoia can run it with limitations. Xcode 26 is required to compile the containerization components. Container functionality also depends on Apple's Containerization Framework, and the Apple Container CLI must be installed and available on `PATH`.

Installation is available either by cloning the repository or by installing the `acms` package in a Python virtual environment. The recommended startup method is the repository's `start-acms.sh` script. Alternatively, launch the Python entry point directly and provide `--port` and `--host` options.

After starting the process, add the HTTP endpoint to the MCP client. The provided command uses `claude mcp add --transport http acms http://localhost:8765/mcp`. The server output can be redirected to a log file when launching it in the background.

## Tools and capabilities

ACMS exposes programmatic access to Apple's container CLI through MCP. This supports agent-directed container tasks, including the documented example of creating an Ubuntu x64 container.

The repository also includes end-to-end testing instructions.

## Limitations and notes

The ACMS MCP server is designed for a specific Apple platform stack rather than general macOS or Linux hosts. Apple Silicon, the stated macOS and Xcode versions, Apple's framework, and the CLI are all prerequisites. Running on Sequoia is documented as possible only with limitations.

The README warns that the setup is not secure, particularly when exposed from a remote Mac on a home network. It also cautions that an AI client may cause data loss while attempting to help. Treat remote exposure and agent permissions as risks, and avoid using the service with data or actions that cannot be safely recovered.

_Full upstream README: https://allmcps.com/mcp/acms/readme_