Skip to main content
Glama
kunwarmahen

Podman MCP Server

by kunwarmahen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Podman MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • ContainMind

      Ashfaqbs
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage and analyze containers across Docker and Podman through natural language, providing unified inspection, monitoring, and diagnostics.
      3
      -

    • 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

    • Docker-MCPilotS

      sopyk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage Docker containers through a secure MCP interface, supporting container lifecycle operations, log inspection, resource monitoring, and system diagnostics with role-based access control.
      3
      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

    A3.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific container operations with no overlap. For example, list_containers, run_container, stop_container, and remove_container each handle different lifecycle stages without ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout, such as list_containers, run_container, and stop_container. This predictability makes the tool set easy to navigate and understand.

    Tool Count5/5

    With 12 tools, the server is well-scoped for container management, covering essential operations like listing, running, stopping, and inspecting containers. Each tool serves a clear purpose without bloat.

    Completeness5/5

    The tool set provides complete CRUD and lifecycle coverage for container management, including create (run_container), read (list_containers, container_info), update (restart_container, start/stop), and delete (remove_container), with no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources