$ loading_
Let AI agents manage, build, and diagnose Linux containers on macOS.
This MCP tool is described as managing, building, inspecting, and diagnosing Linux containers on macOS, which inherently implies local code execution and access to container/system resources, so it should be used with caution. The materials show no required secrets or fixed remote endpoints, and it is open-source under Apache 2.0, but adoption is minimal and maintenance status is unknown, limiting supply-chain confidence.
The materials explicitly state that no keys or environment variables are required, and there is no stated token collection, storage, or credential forwarding; based on the provided facts, credential exposure appears low.
No remote endpoints are declared in the materials, and the objective checks do not provide evidence of outbound network behavior; from the available description alone, there is no factual indication that user data is sent to external services.
The system explicitly flags executes-code, and the described functions—managing, building, and diagnosing containers—indicate local process execution and use of container-related system capabilities. This is a normal but sensitive local capability for this class of MCP tool and warrants controlled use.
To manage and inspect containers, the tool likely needs access to local container resources, images, configurations, and related files/logs. The exact access boundary is not documented, but there is no concrete evidence of permissions exceeding its stated purpose.
Positive factors include an auditable open-source repository and an Apache 2.0 license. However, the source is a third-party registry listing, the GitHub repository has 0 stars, no README is provided, and maintenance status is unknown, so community validation and maintenance assurance are limited; review source and release integrity before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "container-mcp" yet — see the docs or source repo.
Using container-mcp on macOS, build a Linux container named webapp-dev from the Dockerfile in the current directory, start it, and return the build result, container status, and exposed port information.
Returns the build and startup results, including image/container details, running status, and port information.
Use container-mcp to inspect the container named api-test and output its base image, environment variables, mounted volumes, network configuration, and resource limits, then summarize any potential configuration issues in bullet points.
Provides a detailed container configuration report and summarizes configuration risks that may affect runtime.
Use container-mcp to diagnose why the Linux container named worker-service fails to start properly. Check logs, exit codes, health check status, and recent changes, then provide likely causes and remediation suggestions.
Outputs diagnostic findings with key log clues, likely causes, and actionable remediation recommendations.
Run AI agents in VM-isolated sandboxes on Mac for safer execution.
Manage Podman containers via REST API for creation, inspection, and operations.
Expose read-only macOS app data to AI agents through MCP.
Use AI to generate and optimize Docker and Kubernetes containerization workflows.
Manage Linux services, processes, disks, networks, and logs through AI agents.
Create, manage, and compose AI agents for MCP-compatible clients and tools.