Log inSubmit server
ACMS logo

ACMS

Exposes Apple's container CLI to AI clients through MCP on Apple Silicon Macs.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install ACMS

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "acms": {
      "command": "uvx",
      "args": [
        "acms"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Apple's Container CLI becomes available to AI clients through the ACMS MCP server on macOS. It runs locally or over HTTP/S and forwards MCP requests to the installed CLI after Apple container services are started. Use it when an agent needs programmatic access to Apple's container tooling from a supported Mac environment. The project requires Apple Silicon, macOS 26 or later, Xcode 26, the Apple Containerization Framework, and the Container CLI.

Use cases

  • Create containers through an AI client
  • Expose Apple's container CLI over HTTP
  • Run container tasks from a remote MCP client
  • Test Apple container workflows with Claude

Key features

  • MCP access to Apple's Container CLI
  • Local or HTTP/S operation
  • Configurable host and port
  • Python package installation
  • End-to-end testing guidance

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · acms (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit10mo agoMost recent push to the default branch.

How ACMS works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ACMS

ACMS is an MCP server that connects AI clients to Apple's Container CLI on macOS and exposes programmatic access to container operations through MCP. It can run locally or over HTTP/S, letting a client send requests to the CLI after Apple container services are started.

Install it by cloning the repository or running `pip install acms` inside a Python virtual environment. Apple Container CLI and its required Apple components must already be installed, and the CLI must be available on `PATH`.

ACMS requires an Apple Silicon Mac and targets macOS 26 or later. Xcode 26, Apple's Containerization Framework, and the Apple Container CLI are also required.

Connect Claude over HTTP with `claude mcp add --transport http acms http://localhost:8765/mcp`. Start Apple container services first, then launch ACMS on the configured host and port.

No; the README explicitly warns that ACMS is not secure, especially when running on a remote Mac reachable from a home network. Remote exposure should be treated cautiously because an AI client may cause data loss.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewACMS AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/acms?style=directory)](https://allmcps.com/mcp/acms)
HTML Embed
<a href="https://allmcps.com/mcp/acms"><img src="https://allmcps.com/api/badge/acms?style=directory" alt="ACMS on AllMCPs" /></a>