About MCP Podman
MCP server for managing Podman through its REST API, aimed at users operating rootful or rootless Podman environments. It covers containers, images, pods, networks, volumes, and system information.
Key features
- 01List, inspect, and control containers
- 02View logs, processes, and resource usage
- 03Manage images and image cleanup
- 04Create and control pods
- 05Inspect networks and volumes
- 06View Podman system and disk usage
Use cases
- 01Check container status and logs
- 02Start, stop, or restart containers
- 03Review image and pod inventories
- 04Inspect Podman resource and disk usage
MCP support
Exposes Podman container, image, pod, network, volume, and system-management tools to MCP clients through the Podman REST API.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEmcp-podman-crunchtools
MCP server for Podman container management via the Podman REST API. Manages containers, images, pods, networks, volumes, and system info. Supports both rootful and rootless Podman.
Installation
# uvx (zero-install)
uvx mcp-podman-crunchtools
# pip
pip install mcp-podman-crunchtools
# Container
podman run -v /run/podman/podman.sock:/run/podman/podman.sock:z \
--security-opt label=type:container_runtime_t \
quay.io/crunchtools/mcp-podman
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
PODMAN_SOCKET | No | Auto-detect | Unix socket path |
PODMAN_SOCKET_FILE | No | — | File containing socket path |
PODMAN_TIMEOUT | No | 30 | Request timeout in seconds |
Socket auto-detection order:
$XDG_RUNTIME_DIR/podman/podman.sock(rootless)/run/user/$UID/podman/podman.sock(rootless fallback)/run/podman/podman.sock(rootful)
Claude Code Integration
claude mcp add mcp-podman-crunchtools \
--env PODMAN_SOCKET=/run/podman/podman.sock \
-- uvx mcp-podman-crunchtools
Tools (30)
Containers (12)
| Tool | Description |
|---|---|
container_list | List containers |
container_inspect | Get container details; environment values are redacted, names kept |
container_start | Start a container |
container_stop | Stop a container |
container_restart | Restart a container |
container_kill | Send signal to container |
container_rm | Remove a container |
container_logs | Get container logs |
container_top | List processes |
container_stats | Resource usage |
container_create | Create a container |
container_prune | Remove stopped containers |
Images (5)
| Tool | Description |
|---|---|
image_list | List images |
image_inspect | Get image details |
image_pull | Pull from registry |
image_rm | Remove an image |
image_prune | Remove unused images, with the options of podman image prune (all, external, build_cache, filters) |
Pods (7)
| Tool | Description |
|---|---|
pod_list | List pods |
pod_inspect | Get pod details |
pod_start | Start a pod |
pod_stop | Stop a pod |
pod_restart | Restart a pod |
pod_rm | Remove a pod |
pod_create | Create a pod |
Networks (2)
| Tool | Description |
|---|---|
network_list | List networks |
network_inspect | Get network details |
Volumes (2)
| Tool | Description |
|---|---|
volume_list | List volumes |
volume_inspect | Get volume details |
System (2)
| Tool | Description |
|---|---|
system_info | Podman system info |
system_df | Disk usage |
License
AGPL-3.0-or-later
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.