Claude Code Container MCP Server¶

What it is¶

An MCP server that manages containerized Claude Code sessions, transforming the CLI tool into an orchestratable, isolated service. It allows models like Claude 4.8 Opus and GPT-5.5 to manage their own execution environments via Docker.

What problem it solves¶

It enables AI assistants to create and control isolated Claude Code instances programmatically. It provides Docker-based isolation, multi-session management, and support for AWS Bedrock, making it suitable for enterprise AI-to-AI workflows. It solves the risk of an agent performing destructive actions on a host machine by confining the agent to a disposable container.

Where it fits in the stack¶

Tool / Orchestration. It provides a managed environment for running other coding agents, following the Agent Protocols for structured tool interaction.

Typical use cases¶

Parallel development workflows (managing different microservices in separate containers).
Automated code reviews in CI/CD pipelines using GitHub Actions.
Enterprise batch operations across multiple legacy projects.
Running Claude Code with AWS Bedrock for enterprise compliance and data residency.

Strengths¶

Isolation: Docker containers protect the host system and isolate projects from each other.
Scalability: Can run dozens of Claude Code sessions simultaneously on a single host.
AWS Bedrock Integration: Native support for AWS enterprise LLM endpoints for secure inference.
Programmable API: Full MCP tools for creating, executing, and destroying sessions programmatically.

Limitations¶

Docker Dependency: Requires access to the Docker daemon, which has significant security implications if not managed correctly.
TOS Compliance: This is an unofficial containerization; users must comply with Anthropic's Terms of Service.
Configuration Complexity: Manual processing required for some complex MCP configurations within containers.

When to use it¶

When you need "an agent in your agent" to perform complex coding tasks in isolated environments.
When you want to automate Claude Code actions via a central orchestrator or CI/CD pipeline.
For enterprise deployments requiring AWS Bedrock instead of direct Anthropic API access.

When not to use it¶

On systems where you cannot or should not provide Docker daemon access to an AI agent.
For simple CLI interactions where the standard Claude Code installation is sufficient.
If you lack sufficient system resources (RAM/CPU) to run multiple concurrent Docker containers.

Getting started¶

Claude Code Container MCP provides a bridge between high-level orchestration and low-level agent execution.

1. Prerequisites¶

Docker installed and running on the host.
MCP client (like Claude Desktop or Desktop Commander MCP).

2. Installation¶

npm install -g @democratize-technology/claude-code-container-mcp

3. Configuration (Claude Desktop)¶

{
  "mcpServers": {
    "claude-container": {
      "command": "claude-code-container-mcp",
      "args": ["--docker-socket", "/var/run/docker.sock"]
    }
  }
}

CLI examples¶

1. Listing active sessions¶

Check currently running Claude Code containers and their status:

claude-code-container-mcp list

2. Manual session cleanup¶

Force-stop and remove all managed containers to free up resources:

claude-code-container-mcp prune --force

3. Debugging a session¶

View logs for a specific containerized agent session to diagnose failures:

claude-code-container-mcp logs --session <session-id>

API examples¶

1. Creating a Session (Anthropic API)¶

Automate the creation of an isolated Claude Code session for a specific project directory.

{
  "tool": "create_session",
  "arguments": {
    "projectPath": "/home/user/workspace/web-app",
    "sessionName": "frontend-refactor",
    "apiKey": "sk-ant-..."
  }
}

2. Creating a Session (AWS Bedrock)¶

Use enterprise-grade models via AWS Bedrock for the session for enhanced security.

{
  "tool": "create_session",
  "arguments": {
    "projectPath": "/home/user/workspace/data-pipeline",
    "useBedrock": true,
    "awsRegion": "us-east-1",
    "bedrockModel": "us.anthropic.claude-3-5-sonnet-20240620-v1:0"
  }
}

3. Executing Commands in Session¶

Send a prompt to an active Claude Code container to perform work asynchronously.

{
  "tool": "execute_in_session",
  "arguments": {
    "sessionId": "abc-123-xyz",
    "prompt": "Refactor the authentication middleware to use JWT instead of sessions."
  }
}

Sources / References¶

Contribution Metadata¶

Last reviewed: 2026-06-30
Confidence: high