Mcp Containerd

What is Mcp Containerd about?

Mcp Containerd provides an MCP server implementation that interfaces directly with Containerd's CRI APIs. It enables AI agents or other MCP clients to perform container and image operations through natural‑language commands.

How to use Mcp Containerd?

1. Prerequisites: Install Rust toolchain, ensure Containerd is running, and have protobuf tools available.
2. Build: cargo build --release
3. Run: cargo run --release – the server connects by default to unix:///run/containerd/containerd.sock.
4. Interact: Use the simple-chat-client example (found in the Rust SDK repository) to send textual prompts; the server translates them into CRI calls.

Key features

• Full implementation of Containerd CRI Runtime Service (pod sandbox, container lifecycle, exec, status).
• Full implementation of Containerd CRI Image Service (list, pull, delete, status, filesystem info).
• Built on the RMCP library, exposing operations as MCP tools (list_containers, list_images, etc.).
• Minimal configuration – works out‑of‑the‑box with default Containerd socket.

Use cases

• Enable AI‑driven orchestration of containers without writing explicit scripts.
• Provide a natural‑language interface for developers to query and manage container workloads.
• Serve as a backend for chat‑based DevOps assistants.
• Integrate with other MCP‑compatible services that need container management capabilities.

FAQ

Q: Which Containerd socket does the server connect to? A: By default it connects to unix:///run/containerd/containerd.sock. Change the endpoint in the source if needed.

Q: Do I need to configure any environment variables? A: No additional environment variables are required beyond having Containerd running.

Q: Can I customize the MCP server configuration? A: Current versions use hard‑coded defaults; future releases will add configurable connection parameters.

Q: How do I interact with the server? A: Use the simple-chat-client example from the Rust SDK, which sends natural‑language prompts and receives tool‑based responses.

Q: What license is the project under? A: Apache-2.0

MCP Containerd

This is an MCP server implemented using the RMCP (Rust Model Context Protocol) library for operating Containerd's CRI interfaces.

Features

• Implements an MCP server using the RMCP library
• Supports all Containerd CRI interface operations
• Provides Runtime Service interfaces
• Provides Image Service interfaces

Prerequisites

• Rust development environment
• Containerd installed and running
• Protobuf compilation tools

Building

cargo build --release

Running

cargo run --release

By default, the service will connect to the unix:///run/containerd/containerd.sock endpoint.

Using with simple-chat-client

The simple-chat-client allows you to interact with the MCP Containerd service: simple-chat-client has moved to simple-chat-client

Example interaction:

> please give me a list of containers
AI: Listing containers...
Tool: list_containers
Result: {"containers":[...]}

> please give me a list of images
AI: Here are the images in your containerd:
Tool: list_images
Result: {"images":[...]}

Service Structure

The MCP server includes the following main components:

• version service: Provides CRI version information
• runtime service: Provides container and Pod runtime operations
• image service: Provides container image operations

CRI Interfaces

Runtime Service

• Create/Stop/Delete Pod Sandbox
• Create/Start/Stop/Delete containers
• Query Pod/container status
• Execute commands in containers

Image Service

• List images
• Get image status
• Pull images
• Delete images
• Get image filesystem information

Configuration

Currently using default configuration. Future versions will support customizing connection parameters through configuration files.

License

Apache-2.0