mcp-podman-crunchtools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PODMAN_SOCKET | No | Unix socket path | Auto-detect |
| PODMAN_TIMEOUT | No | Request timeout in seconds | 30 |
| PODMAN_SOCKET_FILE | No | File containing socket path |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| container_list_toolC | List containers. |
| container_inspect_toolC | Get detailed information about a container. |
| container_start_toolB | Start a stopped container. |
| container_stop_toolC | Stop a running container. |
| container_restart_toolC | Restart a container. |
| container_kill_toolC | Send a signal to a container. |
| container_rm_toolC | Remove a container. |
| container_logs_toolC | Get container logs. |
| container_top_toolB | List processes running inside a container. |
| container_stats_toolC | Get container resource usage statistics. |
| container_create_toolC | Create a new container. |
| container_prune_toolB | Remove all stopped containers. |
| image_list_toolC | List images. |
| image_inspect_toolC | Get detailed information about an image. |
| image_pull_toolB | Pull an image from a registry. |
| image_rm_toolC | Remove an image. |
| image_prune_toolA | Remove unused images, like With no arguments only dangling (untagged, unused) images are removed. |
| pod_list_toolC | List pods. |
| pod_inspect_toolC | Get detailed information about a pod. |
| pod_start_toolC | Start a pod and all its containers. |
| pod_stop_toolC | Stop a pod and all its containers. |
| pod_restart_toolB | Restart a pod and all its containers. |
| pod_rm_toolB | Remove a pod and all its containers. |
| pod_create_toolC | Create a new pod. |
| network_list_toolC | List networks. |
| network_inspect_toolC | Get detailed information about a network. |
| volume_list_toolC | List volumes. |
| volume_inspect_toolB | Get detailed information about a volume. |
| system_info_toolB | Get Podman system information. |
| system_df_toolB | Get Podman disk usage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
Each tool targets a distinct resource+action pair (container_start vs container_stop vs container_kill), and the resource prefix separates container/image/pod/network/volume tools cleanly. Minor potential confusion between container_kill and container_stop, and between prune vs rm, but descriptions clarify these.
Every tool follows the same resource_action_tool pattern (container_list_tool, image_pull_tool, pod_restart_tool), making the surface highly predictable. No mixed conventions.
30 tools is above the comfortable band, but the breadth is justified by six distinct resource domains (container, image, pod, network, volume, system). Each tool earns its place, though the set feels heavy for a single server.
Containers, images, and pods have solid lifecycle coverage (list/inspect/create/start/stop/restart/rm/prune). However, networks and volumes only have list/inspect with no create/rm, and container exec, image build/push, and container run are missing, leaving notable gaps.