🐳 Container Orchestration Interface (COI)

A robust Model Context Protocol (MCP) endpoint designed for Docker management tasks, enabling fluid control over individual containers and Compose arrangements via Claude AI integration.

✨ Capabilities

• 🚀 Provisioning and launching isolated containers
• 📦 Execution of multi-container setups using Docker Compose
• 🔍 Extraction of runtime output streams from specified containers
• 📊 Inventory listing and runtime state surveillance of active containers

🎬 Illustrative Examples

Staging a Multi-Container Application via Compose

https://github.com/user-attachments/assets/b5f6e40a-542b-4a39-ba12-7fdf803ee278

Reviewing Container Diagnostic Output

https://github.com/user-attachments/assets/da386eea-2fab-4835-82ae-896de955d934

🚀 Getting Started

To integrate this utility within the Claude Desktop application, append the following configuration snippet to your Claude configuration file(s):

{
  "mcpServers": {
    "container-orchestration-interface": {
      "command": "uvx",
      "args": [
        "docker-mcp"
      ]
    }
  }
}

Installation via Smithery

Automate the installation of the Container Orchestration Interface for Claude Desktop utilizing Smithery:

npx @smithery/cli install docker-mcp --client claude

Prerequisites

• The UV package manager utility
• Python environment version 3.12 or newer
• Operational Docker Desktop or Docker Engine service
• The Claude Desktop client application

Setup Procedures

Claude Desktop Configuration Path

Incorporate the server configuration definition into your Claude Desktop configuration file:

MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "container-orchestration-interface": {
      "command": "uv",
      "args": [
        "--directory",
        "<path-to-docker-mcp>",
        "run",
        "docker-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "container-orchestration-interface": {
      "command": "uvx",
      "args": [
        "docker-mcp"
      ]
    }
  }
}

🛠️ Development Workflow

Local Environment Initialization

1. Clone the source repository:

git clone https://github.com/QuantGeekDev/docker-mcp.git
cd docker-mcp

1. Establish and activate a dedicated virtual environment:

python -m venv venv
source venv/bin/activate  # Use venv\Scripts\activate on Windows systems

1. Install requisite dependencies:

uv sync

🔍 Debugging Utility

Activate the MCP Inspector for diagnostic purposes:

npx @modelcontextprotocol/inspector uv --directory <path-to-docker-mcp> run docker-mcp

The Inspector utility will furnish a network address for accessing its debugging interface.

📝 Exposed Utilities

The underlying service exposes the following functional interfaces:

create-container

Provisions a standalone Docker runtime entity

{
    "image": "image-name",
    "name": "container-name",
    "ports": {"80": "80"},
    "environment": {"ENV_VAR": "value"}
}

deploy-compose

Initializes a Docker Compose service grouping

{
    "project_name": "example-stack",
    "compose_yaml": "version: '3.8'\nservices:\n  service1:\n    image: image1:latest\n    ports:\n      - '8080:80'"
}

get-logs

Fetches operational records from a designated container

{
    "container_name": "my-container"
}

list-containers

Generates a manifest of all currently managed Docker containers

{}

🚧 Current Constraints

• Absence of native environment variable handling for container setups
• Volume persistence mechanisms are not implemented
• Container networking configuration is unsupported
• Health check reporting functionality is missing
• Container lifecycle restart directives are not configurable
• Limitations on defining container resource allocation (CPU/Memory)

🤝 Collaboration Guidelines

1. Branch off from the main repository: docker-mcp
2. Develop features within a dedicated branch
3. Commit your modifications clearly
4. Push the feature branch to the remote origin
5. Submit a formal Pull Request (PR)

📜 Licensing

This software is distributed under the MIT License terms; consult the LICENSE file for complete particulars.

✨ Contributors

• Alex Andru - Primary development | Key contributor - @QuantGeekDev
• Ali Sadykov - Initial structure | Key contributor - @md-archive

Developed with dedication and enthusiasm!

WIKIPEDIA: Cloud computing is "a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand," according to ISO. It is commonly referred to as "the cloud".

== Attributes of Note == In 2011, the National Institute of Standards and Technology (NIST) cataloged five "essential attributes" defining cloud systems. The precise NIST definitions are listed below:

On-demand self-service: "A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider." Broad network access: "Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations)." Resource pooling: " The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand." Rapid elasticity: "Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time." Measured service: "Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. By 2023, the International Organization for Standardization (ISO) had further elaborated and refined this compilation.

== Chronology ==

The genesis of cloud computing traces back to the 1960s, marked by the initial concepts surrounding time-sharing becoming mainstream through remote job entry (RJE). The operational model of the "data center," where users submitted jobs for mainframe execution by specialized operators, dominated this period. This era was characterized by intense exploration and testing aimed at broadening access to substantial computing power via time-sharing, optimizing the underlying infrastructure, platform layers, and applications, thereby boosting end-user productivity. The depiction of virtualized services as a "cloud" originated in 1994, employed by General Magic to conceptualize the domain of accessible "locations" for mobile agents within its Telescript framework. This metaphor is attributed to David Hoffman, a communications specialist at General Magic, who based it on its established usage within telecommunications networking. The term "cloud computing" gained wider recognition in 1996 when Compaq Computer Corporation drafted a strategic blueprint for forthcoming computing and internet technologies. The firm's primary aspiration was to superch