Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add io.github.manusa-podman-mcp-server -- npx -y podman-mcp-server@0.0.15รันในเทอร์มินัล
{ "mcpServers": { "io.github.manusa-podman-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิด✨ Features | 🚀 Getting Started | 📚 Documentation | 🎥 Demos | ⚙️ Configuration | 🛠️ Tools | 🧑💻 Development
A powerful and flexible MCP server for container runtimes supporting Podman and Docker.
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"
]
}
}
}
Install the Podman MCP server by clicking one of the following links:
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 is the easiest (and cheapest) way to get rolling with artificial intelligence (AI) agents.
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
For detailed setup guides, configuration reference, and feature specifications, see the Documentation.
The Podman MCP server can be configured using command line (CLI) arguments.
You can run the CLI executable either by using npx or by downloading the latest release binary.
# Run the Podman MCP server using npx (in case you have npm installed)
npx podman-mcp-server@latest --help
# Run the Podman MCP server using the latest release binary
./podman-mcp-server --help
The server supports multiple transport modes:
--port) - Modern HTTP transport with both Streamable HTTP and SSE endpoints--sse-port) - Legacy Server-Sent Events transport (deprecated)# Start HTTP server on port 8080 (Streamable HTTP at /mcp and SSE at /sse)
podman-mcp-server --port 8080
# Legacy SSE-only server on port 8080 (deprecated, use --port instead)
podman-mcp-server --sse-port 8080
The server supports multiple Podman backend implementations:
By default, the server auto-detects the best available implementation.
The api implementation is preferred when a Podman socket is available, otherwise the cli implementation is used as a fallback.
Use the --podman-impl flag to force a specific implementation:
# Force CLI implementation
podman-mcp-server --podman-impl=cli
# Force API implementation (requires Podman socket)
podman-mcp-server --podman-impl=api
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.
container_inspect - Displays the low-level information and configuration of a Docker or Podman container with the specified container ID or name
name (string) (required) - Docker or Podman container ID or name to display the informationcontainer_list - Prints out information about the running Docker or Podman containers
container_logs - Displays the logs of a Docker or Podman container with the specified container ID or name
name (string) (required) - Docker or Podman container ID or name to display the logscontainer_remove - Removes a Docker or Podman container with the specified container ID or name (rm)
name (string) (required) - Docker or Podman container ID or name to removecontainer_run - Runs a Docker or Podman container with the specified image name
environment (array) - Environment variables to set in the container. Format: =. Example: FOO=bar. (Optional, add only to set environment variables)imageName (string) (required) - Docker or Podman container image name to runports (array) - Port mappings to expose on the host. Format: :. Example: 8080:80. (Optional, add only to expose ports)container_stop - Stops a Docker or Podman running container with the specified container ID or name
name (string) (required) - Docker or Podman container ID or name to stopimage_build - Build a Docker or Podman image from a Dockerfile, Podmanfile, or Containerfile
containerFile (string) (required) - The absolute path to the Dockerfile, Podmanfile, or Containerfile to build the image fromimageName (string) - Specifies the name which is assigned to the resulting image if the build process completes successfully (--tag, -t)image_list - List the Docker or Podman images on the local machine
image_pull - Copies (pulls) a Docker or Podman container image from a registry onto the local machine storage
imageName (string) (required) - Docker or Podman container image name to pullimage_push - Pushes a Docker or Podman container image, manifest list or image index from local machine storage to a registry
imageName (string) (required) - Docker or Podman container image name to pushimage_remove - Removes a Docker or Podman image from the local machine storage
imageName (string) (required) - Docker or Podman container image name to removeCompile the project and run the Podman MCP server with mcp-inspector to inspect the MCP server.
# Compile the project
make build
# Run the Podman MCP server with mcp-inspector
npx @modelcontextprotocol/inspector@latest $(pwd)/podman-mcp-server
mcp-name: io.github.manusa/podman-mcp-server
A Model Context Protocol (MCP) server for container runtimes (Podman and Docker)
{ "mcpServers": { "io.github.manusa-podman-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Podman ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 A Model Context Protocol (MCP) server for container runtimes (Podman and Docker)