Skip to content
Back to search

podman-mcp-server

Model Context Protocol (MCP) server for container runtimes (Podman and Docker)

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/manusa--podman-mcp-server/badge.svg)](/listings/manusa--podman-mcp-server)

HTML

<a href="/listings/manusa--podman-mcp-server"><img src="/api/listings/manusa--podman-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Desktop

Using npx

If you have npm installed, this is the fastest way to get started with `podman-mcp-server` on Claude Desktop.

Open your `claude_desktop_config.json` and add the mcp server to the list of `mcpServers`:

{
  "mcpServers": {
    "podman": {
      "command": "npx",
      "args": [
        "-y",
        "podman-mcp-server@latest"
      ]
    }
  }
}

VS Code / VS Code Insiders

Install the Podman MCP server by clicking one of the following links:

[<img src="https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF" alt="Install in VS Code">](https://vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522podman%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522podman-mcp-server%2540latest%2522%255D%257D) [<img alt="Install in VS Code Insiders" src="https://img.shields.io/badge/VS_Code_Insiders-VS_Code_Insiders?style=flat-square&label=Install%20Server&color=24bfa5">](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522podman%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522podman-mcp-server%2540latest%2522%255D%257D)

Alternatively, you can install the extension manually by running the following command:

# For VS Code
code --add-mcp '{"name":"podman","command":"npx","args":["-y","podman-mcp-server@latest"]}'
# For VS Code Insiders
code-insiders --add-mcp '{"name":"podman","command":"npx","args":["-y","podman-mcp-server@latest"]}'

Goose CLI

[Goose CLI](https://blog.marcnuri.com/goose-on-machine-ai-agent-cli-introduction) is the easiest (and cheapest) way to get rolling with artificial intelligence (AI) agents.

Using npm

If you have npm installed, this is the fastest way to get started with `podman-mcp-server`.

Open your goose `config.yaml` and add the mcp server to the list of `mcpServers`:

extensions:
  podman:
    command: npx
    args:
      - -y
      - podman-mcp-server@latest

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 227 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Podman MCP Server
  2. [![GitHub License](https://img.shields.io/github/license/manusa/podman-mcp-server)](https://github.com/manusa/podman-mcp-server/blob/main/LICENSE)
  3. [![npm](https://img.shields.io/npm/v/podman-mcp-server)](https://www.npmjs.com/package/podman-mcp-server)
  4. [![PyPI - Version](https://img.shields.io/pypi/v/podman-mcp-server)](https://pypi.org/project/podman-mcp-server/)
  5. [![GitHub release (latest SemVer)](https://img.shields.io/github/v/release/manusa/podman-mcp-server?sort=semver)](https://github.com/manusa/podman-mcp-server/releases/latest)
  6. [![Build](https://github.com/manusa/podman-mcp-server/actions/workflows/build.yaml/badge.svg)](https://github.com/manusa/podman-mcp-server/actions/workflows/build.yaml)
  7. [✨ Features](#features) | [🚀 Getting Started](#getting-started) | [📚 Documentation](#documentation) | [🎥 Demos](#demos) | [⚙️ Configuration](#configuration) | [🛠️ Tools](#tools) | [🧑‍💻 Development](#development)
  8. ## ✨ Features <a id="features"></a>
  9. A powerful and flexible MCP server for container runtimes supporting Podman and Docker.
  10. ## 🚀 Getting Started <a id="getting-started"></a>
  11. ### Claude Desktop
  12. #### Using npx
  13. If you have npm installed, this is the fastest way to get started with `podman-mcp-server` on Claude Desktop.
  14. Open your `claude_desktop_config.json` and add the mcp server to the list of `mcpServers`:
  15. ``` json
  16. {
  17. "mcpServers": {
  18. "podman": {
  19. "command": "npx",
  20. "args": [
  21. "-y",
  22. "podman-mcp-server@latest"
  23. ]
  24. }
  25. }
  26. }
  27. ```
  28. ### VS Code / VS Code Insiders
  29. Install the Podman MCP server by clicking one of the following links:
  30. [<img src="https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF" alt="Install in VS Code">](https://vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522podman%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522podman-mcp-server%2540latest%2522%255D%257D)
  31. [<img alt="Install in VS Code Insiders" src="https://img.shields.io/badge/VS_Code_Insiders-VS_Code_Insiders?style=flat-square&label=Install%20Server&color=24bfa5">](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522podman%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522podman-mcp-server%2540latest%2522%255D%257D)
  32. Alternatively, you can install the extension manually by running the following command:
  33. ```shell
  34. # For VS Code
  35. code --add-mcp '{"name":"podman","command":"npx","args":["-y","podman-mcp-server@latest"]}'
  36. # For VS Code Insiders
  37. code-insiders --add-mcp '{"name":"podman","command":"npx","args":["-y","podman-mcp-server@latest"]}'
  38. ```
  39. ### Goose CLI
  40. [Goose CLI](https://blog.marcnuri.com/goose-on-machine-ai-agent-cli-introduction) is the easiest (and cheapest) way to get rolling with artificial intelligence (AI) agents.
  41. #### Using npm
  42. If you have npm installed, this is the fastest way to get started with `podman-mcp-server`.
  43. Open your goose `config.yaml` and add the mcp server to the list of `mcpServers`:
  44. ```yaml
  45. extensions:
  46. podman:
  47. command: npx
  48. args:
  49. - -y
  50. - podman-mcp-server@latest
  51. ```
  52. ## 📚 Documentation <a id="documentation"></a>
  53. For detailed setup guides, configuration reference, and feature specifications, see the **[Documentation](docs/README.md)**.
  54. ## 🎥 Demos <a id="demos"></a>
  55. ## ⚙️ Configuration <a id="configuration"></a>
  56. The Podman MCP server can be configured using command line (CLI) arguments.
  57. You can run the CLI executable either by using `npx` or by downloading the [latest release binary](https://github.com/manusa/podman-mcp-server/releases/latest).
  58. ```shell
  59. # Run the Podman MCP server using npx (in case you have npm installed)
  60. npx podman-mcp-server@latest --help
  61. ```
  62. ```shell
  63. # Run the Podman MCP server using the latest release binary
  64. ./podman-mcp-server --help
  65. ```
  66. ### Configuration Options
  67. | Option | Description |
  68. |------------------------|--------------------------------------------------------------------------------------------------|
  69. | `--port`, `-p` | Starts the MCP server in HTTP mode with Streamable HTTP at `/mcp` and SSE at `/sse` endpoints. |
  70. | `--output-format`, `-o`| Output format for list commands: `text` (default, human-readable table) or `json`. |
  71. | `--podman-impl` | Podman implementation to use. Auto-detects if not specified. |
  72. | `--sse-port` | **Deprecated.** Use `--port` instead. Starts the MCP server in SSE-only mode. |
  73. | `--sse-base-url` | **Deprecated.** SSE public base URL to use when sending the endpoint message. |
  74. ### Transport Modes
  75. The server supports multiple transport modes:
  76. 1. **STDIO mode** (default) - Communicates via standard input/output
  77. 2. **HTTP mode** (`--port`) - Modern HTTP transport with both Streamable HTTP and SSE endpoints
  78. 3. **SSE-only mode** (`--sse-port`) - Legacy Server-Sent Events transport (deprecated)
  79. ```shell
  80. # Start HTTP server on port 8080 (Streamable HTTP at /mcp and SSE at /sse)
  81. podman-mcp-server --port 8080
  82. # Legacy SSE-only server on port 8080 (deprecated, use --port instead)
  83. podman-mcp-server --sse-port 8080
  84. ```
  85. ### Podman Implementations
  86. The server supports multiple Podman backend implementations:
  87. | Implementation | Description | Priority |
  88. |----------------|-------------|----------|
  89. | `api` | Podman REST API via Unix socket | 100 (preferred) |
  90. | `cli` | Podman/Docker CLI wrapper | 50 (fallback) |
  91. By default, the server **auto-detects** the best available implementation.
  92. The `api` implementation is preferred when a Podman socket is available, otherwise the `cli` implementation is used as a fallback.
  93. Use the `--podman-impl` flag to force a specific implementation:
  94. ```shell
  95. # Force CLI implementation
  96. podman-mcp-server --podman-impl=cli
  97. # Force API implementation (requires Podman socket)
  98. podman-mcp-server --podman-impl=api
  99. ```
  100. The `api` implementation communicates directly with the Podman REST API via Unix socket, while the `cli` implementation shells out to the `podman` or `docker` binary.
  101. ## 🛠️ Tools <a id="tools"></a>
  102. <!-- AVAILABLE-TOOLS-START -->
  103. <details>
  104. <summary>Container</summary>
  105. - **container_inspect** - Displays the low-level information and configuration of a Docker or Podman container with the specified container ID or name
  106. - `name` (`string`) **(required)** - Docker or Podman container ID or name to display the information
  107. - **container_list** - Prints out information about the running Docker or Podman containers
  108. - **container_logs** - Displays the logs of a Docker or Podman container with the specified container ID or name
  109. - `name` (`string`) **(required)** - Docker or Podman container ID or name to display the logs
  110. - **container_remove** - Removes a Docker or Podman container with the specified container ID or name (rm)
  111. - `name` (`string`) **(required)** - Docker or Podman container ID or name to remove
  112. - **container_run** - Runs a Docker or Podman container with the specified image name
  113. - `environment` (`array`) - Environment variables to set in the container. Format: <key>=<value>. Example: FOO=bar. (Optional, add only to set environment variables)
  114. - `imageName` (`string`) **(required)** - Docker or Podman container image name to run
  115. - `ports` (`array`) - Port mappings to expose on the host. Format: <hostPort>:<containerPort>. Example: 8080:80. (Optional, add only to expose ports)
  116. - **container_stop** - Stops a Docker or Podman running container with the specified container ID or name
  117. - `name` (`string`) **(required)** - Docker or Podman container ID or name to stop
  118. </details>
  119. <details>
  120. <summary>Image</summary>
  121. - **image_build** - Build a Docker or Podman image from a Dockerfile, Podmanfile, or Containerfile
  122. - `containerFile` (`string`) **(required)** - The absolute path to the Dockerfile, Podmanfile, or Containerfile to build the image from
  123. - `imageName` (`string`) - Specifies the name which is assigned to the resulting image if the build process completes successfully (--tag, -t)
  124. - **image_list** - List the Docker or Podman images on the local machine
  125. - **image_pull** - Copies (pulls) a Docker or Podman container image from a registry onto the local machine storage
  126. - `imageName` (`string`) **(required)** - Docker or Podman container image name to pull
  127. - **image_push** - Pushes a Docker or Podman container image, manifest list or image index from local machine storage to a registry
  128. - `imageName` (`string`) **(required)** - Docker or Podman container image name to push
  129. - **image_remove** - Removes a Docker or Podman image from the local machine storage
  130. - `imageName` (`string`) **(required)** - Docker or Podman container image name to remove
  131. </details>
  132. <details>
  133. <summary>Network</summary>
  134. - **network_list** - List all the available Docker or Podman networks
  135. </details>
  136. <details>
  137. <summary>Volume</summary>
  138. - **volume_list** - List all the available Docker or Podman volumes
  139. </details>
  140. <!-- AVAILABLE-TOOLS-END -->
  141. ## 🧑‍💻 Development <a id="development"></a>
  142. ### Running with mcp-inspector
  143. Compile the project and run the Podman MCP server with [mcp-inspector](https://modelcontextprotocol.io/docs/tools/inspector) to inspect the MCP server.
  144. ```shell
  145. # Compile the project
  146. make build
  147. # Run the Podman MCP server with mcp-inspector
  148. npx @modelcontextprotocol/inspector@latest $(pwd)/podman-mcp-server
  149. ```
  150. mcp-name: io.github.manusa/podman-mcp-server

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.