mcp-podman-crunchtools
Related Servers
Alternatives to mcp-podman-crunchtools
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI tools to manage containerized applications through Podman, supporting container lifecycle operations, command execution, log viewing, image management, and resource monitoring. Features automatic network discovery for seamless integration with MCP Discovery Hub.12-
- AlicenseNot gradedqualityBmaintenanceEnables management of Podman containers, pods, images, and compose stacks via natural language, with support for container stats, logs, exec, health analysis, and a web dashboard.1MIT
- AlicenseBqualityBmaintenanceMCP server that exposes Podman host management as tools, allowing natural language control of containers, images, volumes, networks, and pods. Includes an administrative console with safety profiles for gated access.18MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Podman and Docker container runtimes, enabling management of containers, images, networks, and volumes via AI assistants.86Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to inspect and operate Docker or Podman containers by checking daemon status, listing containers and images, reading logs, executing commands, running throwaway echo containers, and querying compose projects through a FastMCP stdio interface.Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceProvides a local API to manage Docker containers and volumes, enabling operations like listing, inspecting, starting, stopping, and removing containers, as well as managing volumes, all through HTTP endpoints without shell commands.MIT
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.