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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
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_toolA | Remove all stopped containers. Returns: List of removed container IDs and reclaimed space |
| 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_toolA | Get Podman system information. Returns: System details including version, storage, registries, and runtime |
| system_df_toolA | Get Podman disk usage. Returns: Disk usage by images, containers, and volumes |
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 is clearly scoped by resource prefix (container_, image_, pod_, network_, volume_, system_) and a distinct action suffix. Overlaps such as list vs inspect occur only across clearly different resources, so an agent can reliably choose the right tool.
All tools follow the same predictable snake_case pattern: <resource>_<action>_tool. Minor abbreviations like rm and df are still consistent with the established convention and do not create confusion.
With 30 tools, the surface is heavy for a single MCP server and exceeds the typical well-scoped range. While Podman naturally has many operations, the count feels inflated because several resources expose only list/inspect while others expose extensive lifecycle actions.
Container lifecycle is fairly complete, including create, start, stop, restart, kill, remove, logs, stats, and top. However, major gaps exist for images (no build/push/tag), networks (no create/remove/connect/disconnect), volumes (no create/remove/prune), and pods (no pause/unpause or logs).