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
Running
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-clientExample interaction:
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
- Get image filesystem information
Configuration
Currently using default configuration. Future versions will support customizing connection parameters through configuration files.
License
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
Running
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-clientExample interaction:
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
- Get image filesystem information
Configuration
Currently using default configuration. Future versions will support customizing connection parameters through configuration files.
License
Apache-2.0