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.
      81
      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.
      75 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.4/5.0

    Scored across 36 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources