Podman MCP Server: Podman and Docker containers
Podman MCP Server
An MCP server for Podman and Docker containers: list, run, stop and read logs of containers, build and pull images
- 86 ★ on the repository
- Last commit
Broad access
Why this level
- The tools start and delete containers and images on your machine
- Containers start with environment variables and port mappings chosen by the agent
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/podman-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The tools start and delete containers and images on your machine
- Containers start with environment variables and port mappings chosen by the agent
This is third-party code. Review the repository files before installing.
What it does
Podman MCP Server gives an agent control of containers in Podman or Docker. The container tools are `container_list`, `container_inspect`, `container_logs`, `container_run` with an image, ports and environment variables, `container_stop` and `container_remove`. Images have `image_list`, `image_pull`, `image_push`, `image_build` from a Dockerfile or Containerfile and `image_remove`. `network_list` and `volume_list` are also available. The server picks how to work by itself. The `api` implementation talks to the Podman REST API over a Unix socket and is preferred, while `cli` shells out to the `podman` or `docker` binaries as a fallback. You can force a choice with the `--podman-impl` flag. List output can be text or JSON. The default transport is stdio. With the `--port` flag the server opens HTTP: Streamable HTTP at `/mcp` and SSE at `/sse`. It runs through `npx podman-mcp-server@latest` or a ready release binary, and setups exist for Claude Desktop, VS Code and Goose.
Who it is for. Developers and administrators who use Podman or Docker and want an agent to run, check and build containers.
Good fit when
- A container crashed and the agent must read its logs and settings
- You want to build an image from a Containerfile and run it with port mappings
- The list of images and networks on the machine needs a quick check
- You are moving from Docker to Podman and want one toolset for both
Not a fit when
- You need cluster orchestration in Kubernetes: the server works with a local container runtime
- The agent must not be trusted to delete containers and images: `container_remove` and `image_remove` delete at once
- You need a remote Docker host over SSH with no local socket: that is not described
Example request
Show the logs of the crashed api container and the list of running containers on this machine.MCP
- Transport
- stdio, http, sse
- Authentication
- not required
Limitations
Podman or Docker must be installed. The `api` implementation needs the Podman socket, and without it the server falls back to `cli` and calls the executable. Running through `npx` needs Node.js, or you download the release binary.
There are few tools and they cover basic operations. Volumes are available only as the `volume_list` list, and Compose and pod management are unsupported. The `--sse-port` mode and the `--sse-base-url` option are deprecated, so use `--port` instead.
How to disable. Remove the `podman` entry from the client config, for example `claude_desktop_config.json`. Containers started through the agent stay on the machine and are removed with the usual `podman rm` or `docker rm`.
FAQ
How do I install Podman MCP Server in Claude Desktop?
Add a `podman` entry to `mcpServers` in `claude_desktop_config.json` with the command `npx` and the arguments `-y` and `podman-mcp-server@latest`.
Does the server work with Docker?
Yes. The `cli` implementation calls `docker`, and every tool description mentions Docker or Podman.
What is the difference between the api and cli implementations?
The `api` implementation talks to the Podman REST API over a Unix socket and takes priority. The `cli` implementation calls the `podman` or `docker` binary as a fallback.
How do I enable HTTP mode?
Start the server with the `--port` flag, for example `podman-mcp-server --port 8080`. Streamable HTTP answers at `/mcp` and SSE at `/sse`.
Which tools are there for images?
`image_list`, `image_pull`, `image_push`, `image_build` and `image_remove`.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for managing Docker in natural language: containers, images, networks and volumes, including remote hosts over SSH
Komodo MCP Server runs Docker and Podman containers, stacks and deployments through Komodo: 88 tools, risky ones confirmed
maintenant monitoring MCP server: an agent reads container logs, check history and alerts but never touches the containers
Logs, alerts and container management for Docker and Podman: an MCP server and CLI, with agent rights set by token scope
Official Runpod MCP server: an agent manages Pods, Serverless endpoints, templates and network volumes from chat.
The docker mcp CLI plugin and gateway: MCP servers from Docker's catalog in isolated containers behind one connection point
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Podman MCP Server: Podman and Docker containers (this card) | no | not required | 86 | |
| Docker MCP by QuantGeekDev | no | not required | 504 | Docker only, with no Podman support |
| container-use | yes | not required | 4,089 | isolated environments for an agent's work with no host container management |
| Kubernetes MCP Server | no | not required | 2,244 | manages Kubernetes clusters |
README in short
The README shows installation for Claude Desktop, VS Code and Goose and describes command-line options, transport modes and the two Podman implementations. It ends with a table of container, image, network and volume tools with their arguments and a section on running with mcp-inspector.