Mcp Containerd

What is Mcp Containerd about?

Mcp Containerd implements an MCP server that speaks Containerd's CRI (Container Runtime Interface) APIs. It exposes runtime and image services, allowing AI‑driven tools or other clients to query and control containers and images via the Model Context Protocol.

How to use Mcp Containerd?

1. Prerequisites: Ensure a Rust toolchain, a running Containerd daemon, and protobuf tools are installed.
2. Build: cargo build --release
3. Run: cargo run --release
   • By default the server connects to unix:///run/containerd/containerd.sock.
4. Interact: Use the provided simple-chat-client example (see the linked repository) to send natural‑language requests that are translated into CRI calls.

Key features of Mcp Containerd

• Full implementation of Containerd CRI runtime and image services.
• Runtime Service: pod sandbox lifecycle, container lifecycle, status queries, exec commands.
• Image Service: list, pull, delete, inspect images, retrieve filesystem info.
• Built with the RMCP library, enabling seamless integration with AI agents.
• Simple default configuration; future versions will add customizable connection settings.

Use cases of Mcp Containerd

• AI‑assisted DevOps: Allow LLM agents to manage containers (create, start, stop, delete) through natural language.
• Automated Testing: Programmatically spin up pod sandboxes and run test suites inside containers.
• Dynamic Image Management: Pull and prune images on‑demand based on workload requirements.
• Interactive Debugging: Execute commands inside running containers via chat‑based interfaces.

FAQ from the Mcp Containerd

• Q: Which Containerd socket does the server connect to? A: It defaults to unix:///run/containerd/containerd.sock but can be changed in future configuration files.
• Q: Do I need to install any additional binaries? A: Apart from the Rust toolchain and protobuf compiler, no extra binaries are required.
• Q: Can I run the server on Windows? A: The current implementation targets Unix sockets; Windows support would require modifications.
• Q: How does the server interact with the simple‑chat‑client? A: The client sends MCP messages that the server translates into CRI calls; responses include tool identifiers (e.g., list_containers).

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