
ACMS
- 3 repo stars
- Updated December 22, 2025
- gattjoe/ACMS
ACMS is an MCP server that exposes Apple’s macOS container CLI to your agent over a local HTTP MCP endpoint.
About
Apple Container MCP Server (ACMS) wraps Apple’s container command-line tooling on macOS so coding agents can list, build, run, and manage container workloads through the Model Context Protocol instead of fragile shell one-liners. developers shipping backends or agents from a Mac Studio or MacBook benefit when they want Docker-like flows aligned with Apple’s stack but prefer natural-language ops in Claude Code or Cursor. Install the PyPI-distributed server, start it against the documented localhost MCP URL, and point your client at that endpoint. It shines when you are iterating services locally, reproducing ship-environment bugs, or teaching an agent your container naming conventions—it is not a cross-platform cloud provisioner and it assumes macOS with Apple’s container tooling available. Treat it as operator glue: you still own image security scanning, registry credentials, and production orchestration elsewhere. Version 0.1.0 signals an early integration surface; read the repo before relying on it in unattended CI.
- MCP bridge to Apple’s native container CLI on macOS
- Local streamable-http transport on localhost:8765/mcp
- PyPI package identifier ACMS at version 0.1.0
- stdio-style agent workflows via HTTP MCP on the same host
- GitHub-hosted gattjoe/ACMS for self-hosted inspection
ACMS by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add ACMS -- npx -y gattjoe/ACMSAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 3 |
|---|---|
| Last updated | December 22, 2025 |
| Repository | gattjoe/ACMS ↗ |
What it does
Let your agent drive Apple’s container CLI on macOS for local images, runs, and dev environments without memorizing every subcommand.
Who is it for?
Best when you're on Apple Silicon or Intel Macs and already use Apple’s container CLI and want agent-driven local run/debug loops.
Skip if: Linux-only pipelines, Kubernetes cluster management, or teams without macOS and Apple container tooling installed.
What you get
Your agent can invoke container operations through MCP on localhost so local infra tasks stay repeatable and documented in chat history.
- Agent-executable container build and run actions on Mac
- Documented local MCP endpoint for team reuse
- Faster debug cycles without leaving the IDE chat
By the numbers
- Server version 0.1.0
- 1 PyPI package (identifier ACMS)
- Default transport URL http://localhost:8765/mcp
README.md
ACMS (Apple Container MCP Server)
ACMS is a Model Context Protocol (MCP) server that provides programmatic access to Apple's container CLI tool on macOS. ACMS can be run locally or accessed remotely via HTTP/S.
The point of ACMS is to bring attention to the Containerization package and Container cli efforts. Inspiration for ACMS came from coderunner.
Prerequisites
- Mac with Apple Silicon
- macOS 26+ - It can run on Sequoia with limitations.
- Xcode 26 - required to compile containerization
- Apple Containerization Framework - (required for container functionality)
- Apple Container Cli - installed and in PATH
Quick Start
Install
Either clone the repository or pip install acms in a venv.
Start Apple Container Services
container system start
Start ACMS Server
# Recommended: Use the startup script
./start-acms.sh
# Or start directly with custom options
python3 acms/acms.py --port 8765 --host 127.0.0.1 > acms.log 2>&1 &
Configure MCP Client
Add to your MCP client configuration:
claude mcp add --transport http acms http://localhost:8765/mcp
Usage Examples
"acms create an ubuntu x64 container ..."
Testing
ACMS includes comprehensive end-to-end testing, just tell Claude to run the "ACMS CLAUDE TEST GUIDE".
Security Considerations
This is not secure, especially if you run it on a remote Mac OS endpoint on your home net. Also, you can lose your data when Claude tries to be helpful.

mcp-name: io.github.gattjoe/ACMS
Recommended MCP Servers
How it compares
Local macOS container MCP bridge, not a multi-cloud Terraform or Fly.io deploy skill.
FAQ
Who is ACMS for?
Mac developers who want Claude Code, Cursor, or similar agents to run Apple container CLI workflows through MCP instead of manual terminal typing.
When should I use ACMS?
Use it during operate and local ship prep when you rebuild images, restart services, or debug containerized apps on your Mac development machine.
How do I add ACMS to my agent?
Install the ACMS PyPI package, start the server so it listens at http://localhost:8765/mcp, then add that streamable-http MCP URL in your agent client configuration.