Skip to main content
Glama
WOOWTECH

Woow Podman MCP Server

by WOOWTECH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Woow Podman MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • 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
      -

    • dockerbro

      ramanailearning-cpu
      A
      license
      B
      quality
      C
      maintenance
      MCP server for managing Docker containers, images, and Compose services via natural language, with configurable tool permissions and safety annotations.
      16
      MIT

    • AAP MCP Server

      srinivassrinu842
      A
      license
      B
      quality
      D
      maintenance
      Enterprise-grade MCP server exposing Ansible Automation Platform 2.x as a complete AI interface for LLMs, enabling natural language management of automation resources.
      86
      1
      Apache 2.0
    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 18 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: listing containers, inspecting, starting, stopping, logs, stats, top, healthcheck, exec, plus separate tools for images, pods, volumes, networks, and host-level info. There is no overlap that would cause an agent to misselect.

    Naming Consistency4/5

    The tools consistently use the podman_ prefix and snake_case throughout. Most container operations follow a resource_action pattern (podman_container_start), while some are noun-only (podman_ps, podman_images, podman_events) or compound (podman_system_df), mirroring the podman CLI. The minor style variation is acceptable but not perfectly uniform.

    Tool Count4/5

    With 18 tools, the server is slightly above the typical well-scoped range of 3-15. However, the breadth of Podman features covered (containers, images, pods, volumes, networks, events, exec) justifies the count, and each tool adds value without redundancy.

    Completeness2/5

    The tool set is largely read-oriented and lacks fundamental lifecycle operations. There is no way to create or delete containers, pods, volumes, networks, or images (except pulling). Starting/stopping/restarting and exec provide some control, but the missing CRUD operations are significant gaps for a general Podman server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources