Skip to main content
Glama
Woow Podman MCP Server

Woow Podman MCP Server

by WOOWTECH

Woow Podman MCP Server

English · 繁體中文

This repository holds a nine-product MCP workspace under products/: Headscale, EMQX, Hermes, n8n, Odoo, LiteLLM, Nextcloud, OpenDesign and K8s. Their application/core/frontend source was copied from PaaS on 2026-11-17 and is maintained here since then, without further syncing (see products/PROVENANCE.md). Each product deploys with its own rootless Podman Quadlet, port, volume and credentials. Product containers do not mount the Podman socket.

products/deploy/manage.sh list
products/deploy/manage.sh emqx install --dry-run \
  --release-manifest /path/to/reviewed-release.json \
  --source-checkout /path/to/merged-canonical-checkout
products/deploy/manage.sh emqx install \
  --release-manifest /path/to/reviewed-release.json \
  --source-checkout /path/to/merged-canonical-checkout
products/deploy/manage.sh emqx upgrade \
  --release-manifest /path/to/reviewed-release.json \
  --source-checkout /path/to/merged-canonical-checkout

Product install and upgrade require one of two things:

  • an independently reviewed release manifest, clean source checkouts and an exact local image ID;

  • for an owner-approved unsigned release, --skip-release-signature with an image that products/deploy/build-release-images.sh built from merged main.

See the release proof and trust limits. The paths above are placeholders. Product installers reject --rebuild and require a prebuilt, reviewed image.

Headscale retains its dedicated guide, including its default http://127.0.0.1:18081/ GUI, Origin settings and backups.

Retired: the Podman host MCP

Until 2026-11-14 the repository root also held a Podman host MCP: the woow_podman_mcp_server MCP server and its podman_mcp_admin console. They exposed this host's Podman through the libpod API. The owner retired it, and Pi Web now covers that work. Its last source is kept in the git tag archive/podman-host-mcp-20261114.

scripts/lib/quadlet-lib.sh stays at the root because the product installers source it. It is vendored from Woow_quadlet_migration_plan, and .github/workflows/tests.yml checks it.

Related MCP server: AAP MCP Server

Layout

products/                   the nine products: product source (copied from PaaS), deploy scripts, Quadlets
docs/                       plans and the release provenance guard
scripts/lib/                vendored quadlet-lib (sourced by products/deploy)
tests/                      quadlet-lib checks (lib-version.sh, lock-release.sh)
.github/workflows/          products CI, Headscale CI, quadlet-lib and credential checks

Available Tools

18 tools
podman_container_execA
Destructive

在既有 container 內執行指令,回傳 stdout/stderr 與 exit code。 stderr 行會以 'E| ' 前綴標示(tty=true 時為 raw、無前綴)。

Inputs: name (required), command (required), tty, user, +1 more. Returns: result

podman_container_healthcheckB
Read-only

執行並回報 container 的 healthcheck 結果。

Inputs: name (required). Returns: result

podman_container_inspectA
Read-only

Inspect 單一 container 的完整設定/狀態。輸出很大,只查你要的那一個。

Inputs: name (required), section. Returns: result

podman_container_logsA
Read-only

取 container logs。預設只取最後 200 行;stderr 行會以 'E| ' 前綴標示。

Inputs: name (required), grep, tail, since, +4 more. Returns: result

podman_container_restartC
Idempotent

重啟 container。

Inputs: name (required), timeout. Returns: result

podman_container_startC
Idempotent

啟動 container。

Inputs: name (required). Returns: result

podman_container_statsB
Read-only

container 即時資源用量(單次快照,不 streaming)。

Inputs: all, names. Returns: result

podman_container_stopA
Idempotent

停止 container(預設 10 秒後 SIGKILL)。

Inputs: name (required), timeout. Returns: result

podman_container_topA
Read-only

列出 container 內的 process (podman top)。

Inputs: name (required), ps_args. Returns: result

podman_eventsA
Read-only

讀取 podman 事件流(有界,不會卡住)。查故障時間線很好用。

Inputs: limit, since, until, filters. Returns: result

podman_image_pullA

從 registry 拉 image。會等到拉完,大 image 請留意 timeout。

Inputs: reference (required), policy, tls_verify. Returns: result

podman_imagesB
Read-only

列出本機 images。

Inputs: all, format, filters. Returns: result

podman_infoA
Read-only

Podman host 概況:版本、OS、runtime、rootless、資源用量。

Inputs: format. Returns: result

podman_networksC
Read-only

列出 networks。

Inputs: format. Returns: result

podman_podsB
Read-only

列出 pods 與其中的 containers。

Inputs: format, filters. Returns: result

podman_psA
Read-only

列出 containers。預設只列 running,all=true 含已停止。

Inputs: all, format, filters. Returns: result

podman_system_dfB
Read-only

磁碟用量統計 (podman system df)。

Inputs: no named parameters. Returns: result

podman_volumesA
Read-only

列出 volumes。

Inputs: format. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

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