mcp-containerd

What is mcp-containerd?

mcp-containerd is an MCP (Model Context Protocol) server implemented in Rust that enables interaction with Containerd's Container Runtime Interface (CRI). It provides a way to manage containers and images through a standardized protocol.

How to use mcp-containerd?

To use mcp-containerd, you need a Rust development environment and Containerd installed and running. You can build the project using cargo build --release and run it with cargo run --release. By default, it connects to unix:///run/containerd/containerd.sock. You can interact with it using a client like simple-chat-client (available in the rust-sdk examples).

Key Features of mcp-containerd

• MCP Server Implementation: Built using the RMCP (Rust Model Context Protocol) library.
• Containerd CRI Interface Support: Supports all operations defined by the Containerd CRI, including Runtime Service and Image Service interfaces.
• Runtime Service: Provides functionalities for creating, stopping, deleting Pod Sandboxes, creating, starting, stopping, and deleting containers, querying Pod/container status, and executing commands within containers.
• Image Service: Offers capabilities for listing, getting status, pulling, and deleting images, as well as retrieving image filesystem information.

Use Cases of mcp-containerd

mcp-containerd can be used in scenarios where you need programmatic control over Containerd. This includes:

• Container Orchestration: Building custom container orchestration systems that interact directly with Containerd.
• Development and Testing: Creating tools for testing and managing containerized applications.
• Automation: Automating container and image management tasks within a development or deployment pipeline.

FAQ from mcp-containerd

Q: What are the prerequisites for running mcp-containerd? A: You need a Rust development environment and Containerd installed and running.

Q: How do I build mcp-containerd? A: You can build it using cargo build --release.

Q: How do I run mcp-containerd? A: You can run it using cargo run --release. It will connect to unix:///run/containerd/containerd.sock by default.

Q: Can I configure the connection parameters? A: Currently, it uses default configuration. Future versions are planned to support customizable connection parameters through configuration files.

Q: What kind of services does mcp-containerd provide? A: It provides version, runtime, and image services for managing CRI operations.

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