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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
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_toolB | 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_toolA | List processes running inside a container. |
| container_stats_toolB | 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_toolB | List images. |
| image_inspect_toolB | 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. Returns: List of removed image IDs and reclaimed space |
| pod_list_toolC | List pods. |
| pod_inspect_toolC | Get detailed information about a pod. |
| pod_start_toolA | Start a pod and all its containers. |
| pod_stop_toolA | Stop a pod and all its containers. |
| pod_restart_toolA | Restart a pod and all its containers. |
| pod_rm_toolA | Remove a pod and all its containers. |
| pod_create_toolC | Create a new pod. |
| network_list_toolC | List networks. |
| network_inspect_toolB | Get detailed information about a network. |
| volume_list_toolB | List volumes. |
| volume_inspect_toolB | Get detailed information about a volume. |
| service_list_toolA | List systemd units that manage Podman containers. Only shows units whose ExecStart contains /usr/bin/podman. Non-container services (sshd, firewalld, etc.) are excluded. Returns: List of Podman container service units with status |
| service_status_toolA | Get the status of a Podman container systemd unit. |
| service_restart_toolA | Restart a Podman container systemd unit. This is the correct way to bounce containers on systems where containers are managed by systemd. Using podman restart directly would conflict with systemd's process management. |
| service_start_toolB | Start a Podman container systemd unit. |
| service_stop_toolB | Stop a Podman container systemd unit. |
| service_logs_toolA | Get journal logs for a Podman container systemd unit. |
| 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 36 tools
Every tool has a distinct resource-action pair (e.g., container_list, container_inspect) with clear boundaries. Pod, image, network, volume, and service tools are fully separated, and even similar actions like restart across containers and services are contextually unambiguous.
All tools follow the identical pattern `<resource>_<action>_tool` using lowercase with underscores. This is perfectly consistent across all 36 tools, making the API predictable and easy to navigate.
With 36 tools, the server covers a broad range of Podman functionality across seven resource types. While on the heavier side, each tool serves a specific purpose and aligns with the comprehensive scope of Podman management. The count is slightly above the ideal but justified by the domain's complexity.
Core container and image lifecycle operations are well covered, but notable gaps exist: networks and volumes only have list/inspect (no create or remove), container exec is missing, and image build/push are absent. These omissions make the surface incomplete for a full Podman management tool.