
MCP Podman
io.github.crunchtoolsPublished by GitHub account crunchtoolsv0.1.1Updated Oct 24, 2026
MCP server for Podman container management via the Podman REST API
Overview
A local MCP server that lets an assistant manage Podman containers, images, pods, networks and volumes through the Podman REST API.
- What you can do
- List, inspect, create, start, stop, restart, kill, remove and prune containers, and read their logs, processes and resource usage. List, inspect, pull, remove and prune images. List, inspect, create, start, stop, restart and remove pods. List and inspect networks and volumes. Show Podman system info and disk usage.
- When to use it
- Useful when you run Podman on the same machine and want an assistant to inspect or operate containers, pods, images and storage without typing commands yourself, for both rootful and rootless setups.
- Requirements
- Runs locally as a Python package (uvx or pip) or as a container, and needs access to the Podman Unix socket. The socket path is auto-detected, or set with PODMAN_SOCKET or PODMAN_SOCKET_FILE; PODMAN_TIMEOUT optionally sets the request timeout.
Installation
In SourceWeft
- Open MCP Podman in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-podman-crunchtools
MCP server for Podman container management via the Podman REST API. Manages containers, images, pods, networks, volumes, and system info. Supports both rootful and rootless Podman.
Installation
Configuration
Socket auto-detection order:
$XDG_RUNTIME_DIR/podman/podman.sock(rootless)/run/user/$UID/podman/podman.sock(rootless fallback)/run/podman/podman.sock(rootful)
Claude Code Integration
Tools (30)
Containers (12)
Images (5)
Pods (7)
Networks (2)
Volumes (2)
System (2)
License
AGPL-3.0-or-later
Source: README.md at commit f70f67d
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts