Manage Containerd Runtime and Image Services
mcp-containerd manages Containerd via CRI: pods, containers, and images, through 14 tools built on RMCP in Rust.
1.0.0Add to Favorites
Why it matters
Automate the management of your containerized applications by providing a robust server for interacting with Containerd's runtime and image services. This asset enables fine-grained control over container lifecycles and image operations.
Outcomes
What it gets done
Manage container creation, starting, stopping, and deletion.
Control Pod sandbox lifecycles.
List, pull, and delete container images.
Query container and image status.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-mcp-containerd | bash Capabilities
Tools your agent gets
Lists all containers in containerd
Lists all images in containerd
Provides CRI version information
Creates a Pod sandbox
Stops a Pod sandbox
Deletes a Pod sandbox
Creates a container
Starts a container
Overview
mcp-containerd MCP Server
mcp-containerd gives an AI assistant CRI-based control over Containerd: pod sandbox and container lifecycles, and image operations, via 14 tools. Use it when an AI assistant needs to inspect or manage a Containerd runtime's pods, containers, or images.
What it does
mcp-containerd is an MCP server implemented in Rust using the RMCP library for managing Containerd, supporting the full CRI (Container Runtime Interface) surface across both runtime and image services. It gives an AI assistant direct control over pod sandboxes, containers, and images on a Containerd instance, rather than requiring you to run ctr or crictl commands by hand.
When to use - and when NOT to
Use it when you want an AI assistant to inspect or manage a Containerd runtime: listing containers and images, creating and managing Pod sandboxes, starting or stopping containers, pulling or deleting images, or checking CRI version and image filesystem information. It requires a running Containerd instance, connecting by default to unix:///run/containerd/containerd.sock, plus a Rust build environment and Protobuf compilation tools to build it from source. Since it can create, start, stop, and delete real containers and pods, it should be treated with the same care as direct ctr/crictl access.
Capabilities
list_containers and list_images enumerate what's running or stored in Containerd, and version reports CRI version information. Pod sandbox lifecycle is covered by create_pod_sandbox, stop_pod_sandbox, and delete_pod_sandbox. Container lifecycle is covered by create_container, start_container, stop_container, and delete_container. Image operations include get_image_status, pull_images, delete_images, and get_image_filesystem_info. Together these cover the Runtime Service and Image Service interfaces of the CRI spec, plus command execution inside containers and pod/container status queries.
How to install
Build from source with Cargo:
cargo build --release
By default the server connects to unix:///run/containerd/containerd.sock. Run mcp-containerd -t http to serve over HTTP streaming instead of the default transport, or mcp-containerd --help for the full command-line options.
Who it's for
Platform and infrastructure engineers running Containerd who want an AI assistant to inspect and manage pods, containers, and images directly through the CRI interface, instead of running ctr or crictl commands by hand. Example requests it's built to answer include simply asking for a list of containers or a list of images, with the assistant mapping that directly to list_containers or list_images.
Source README
MCP server implemented in Rust using the RMCP library for managing Containerd, supporting all CRI interface operations including runtime and image services.
Installation
From Source Code
cargo build --release
Available Tools
| Tool | Description |
|---|---|
list_containers |
Lists all containers in containerd |
list_images |
Lists all images in containerd |
version |
Provides CRI version information |
create_pod_sandbox |
Creates a Pod sandbox |
stop_pod_sandbox |
Stops a Pod sandbox |
delete_pod_sandbox |
Deletes a Pod sandbox |
create_container |
Creates a container |
start_container |
Starts a container |
stop_container |
Stops a container |
delete_container |
Deletes a container |
get_image_status |
Gets image status |
pull_images |
Pulls container images |
delete_images |
Deletes container images |
get_image_filesystem_info |
Gets image filesystem information |
Features
- Implements MCP server using the RMCP library
- Supports all Containerd CRI interface operations
- Provides Runtime Service interfaces
- Provides Image Service interfaces
- Supports ctr interface
- Pod Sandbox create/stop/delete operations
- Container create/start/stop/delete operations
- Pod/container status queries
- Command execution in containers
- Image listing, pulling, and deletion
Usage Examples
please give me a list of containers
please give me a list of images
Notes
Requires a Rust development environment, an installed and running Containerd instance, and Protobuf compilation tools. By default, connects to the unix:///run/containerd/containerd.sock endpoint. Can be run with 'mcp-containerd -t http' for HTTP streaming or 'mcp-containerd --help' for help information.
FAQ
Common questions
Trust
How it checks out
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.