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
      A
      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
      D
      maintenance
      MCP server for Podman and Docker container runtimes, enabling management of containers, images, networks, and volumes via AI assistants.
      85
      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.
      33 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool is clearly scoped by resource prefix (container_, image_, pod_, network_, volume_, system_) and a distinct action suffix. Overlaps such as list vs inspect occur only across clearly different resources, so an agent can reliably choose the right tool.

    Naming Consistency5/5

    All tools follow the same predictable snake_case pattern: <resource>_<action>_tool. Minor abbreviations like rm and df are still consistent with the established convention and do not create confusion.

    Tool Count2/5

    With 30 tools, the surface is heavy for a single MCP server and exceeds the typical well-scoped range. While Podman naturally has many operations, the count feels inflated because several resources expose only list/inspect while others expose extensive lifecycle actions.

    Completeness3/5

    Container lifecycle is fairly complete, including create, start, stop, restart, kill, remove, logs, stats, and top. However, major gaps exist for images (no build/push/tag), networks (no create/remove/connect/disconnect), volumes (no create/remove/prune), and pods (no pause/unpause or logs).

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources