Developer toolsPublic source

Containers MCP Server

Complete Docker management for AI agents — containers, images, networks, volumes, compose, and system operations via native socket connection. 42 tools with zero configuration.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides containers capabilities through a typed MCP contract.

Architecture

How Containers MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Containers MCP Server

Validates the request and owns 42 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Containers MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Containers MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

42 named tools

list_containers

List containers (include stopped with all=true)

see documentation

inspect_container

Full details: config, mounts, network, state

see documentation

run_container

Run a new container from an image

see documentation

stop_container

Gracefully stop a container

see documentation

kill_container

Force kill (SIGKILL)

see documentation

remove_container

Remove a stopped container

see documentation

restart_container

Restart a container

see documentation

pause_container

Freeze all processes

see documentation

unpause_container

Resume a paused container

see documentation

rename_container

Rename a container

see documentation

get_logs

Get stdout/stderr logs

see documentation

exec_container

Execute command inside container

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

42 see documentation

Review the server documentation and deployment credentials before enabling it for an agent.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Resources

ADK MCP SDKrmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-containers

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-containers",
    ["mcp-containers"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Api Reference ↗docs/api-reference.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring