Woow Podman MCP Server
# Woow Podman MCP Server
**English** · [繁體中文](README_zh-TW.md)
This repository holds a [nine-product MCP workspace](products/README.md) 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](products/PROVENANCE.md)). Each product deploys with
its own rootless Podman Quadlet, port, volume and credentials. Product
containers do not mount the Podman socket.
```bash
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](docs/release-provenance-guard.md).
The paths above are placeholders. Product installers reject `--rebuild` and
require a prebuilt, reviewed image.
Headscale retains its [dedicated guide](products/deploy/headscale/README.md),
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.
## 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
```
TDQS
Scored across 18 tools
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.
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.
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.
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.