Podman MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Binding host | 0.0.0.0 |
| MCP_PORT | No | Server port | 3001 |
| MCP_TRANSPORT | No | Transport mode (http, streamable-http, or stdio) | stdio |
| MCP_SERVER_NAME | No | Display name | Podman MCP Server |
| MCP_ENABLE_BROADCAST | No | Enable/disable broadcasting | true |
| MCP_BROADCAST_INTERVAL | No | Seconds between announcements | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_containersB | List containers (running by default, all if requested). |
| container_infoB | Inspect a container by name or ID. |
| start_containerB | Start a stopped container. |
| stop_containerB | Stop a running container. |
| restart_containerB | Restart a container. |
| container_logsB | Get logs from a container. |
| run_containerC | Run a new container. |
| remove_containerC | Remove a container. |
| exec_containerB | Execute a command inside a container. |
| list_imagesB | List container images. |
| pull_imageB | Pull a container image from a registry. |
| container_statsB | Get resource usage statistics for containers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose targeting specific container operations with no overlap. For example, list_containers, run_container, stop_container, and remove_container each handle different lifecycle stages without ambiguity.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as list_containers, run_container, and stop_container. This predictability makes the tool set easy to navigate and understand.
With 12 tools, the server is well-scoped for container management, covering essential operations like listing, running, stopping, and inspecting containers. Each tool serves a clear purpose without bloat.
The tool set provides complete CRUD and lifecycle coverage for container management, including create (run_container), read (list_containers, container_info), update (restart_container, start/stop), and delete (remove_container), with no obvious gaps.