Skip to main content
Glama
crunchtools

mcp-podman-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-podman-crunchtools

No user-submitted related servers found.

    Related Servers

    • Podman MCP Server

      kunwarmahen
      F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -

    • podman-mcp

      sandraschi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT

    • Woow Podman MCP Server

      WOOWTECH
      A
      license
      B
      quality
      B
      maintenance
      MCP 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.
      18
      MIT

    • Podman MCP Server

      manusa
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Podman and Docker container runtimes, enabling management of containers, images, networks, and volumes via AI assistants.
      84
      Apache 2.0

    • Docker MCP Server

      santanaraelnew
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 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.
      91 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action, e.g., container stop vs kill vs prune vs rm are unambiguous. Pod, image, network, volume, and system operations are also well separated with no meaningful overlap.

    Naming Consistency5/5

    All 30 tools follow a consistent snake_case resource_action_tool pattern, such as container_list_tool, pod_create_tool, and image_pull_tool. The uniform suffix and verb placement make the naming predictable throughout.

    Tool Count2/5

    With 30 tools, the server exceeds the recommended range and feels over-granular for an MCP surface. Although Podman has a broad domain, several operations could be consolidated or grouped to reduce the tool count.

    Completeness3/5

    Core container, pod, and image lifecycle operations are covered, but notable gaps remain: no network or volume creation/removal, no image build/push, no container exec, and no pod pause/unpause. These missing operations limit common Podman workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources