Containerport

io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026

執行核心 Docker 容器操作：列出、執行、檢查、日誌、鏡像和卷。

AI 翻譯由 AI 模型根據下方的原文描述翻譯，可能有誤。

原文描述

Run core Docker container operations: list, run, inspect, logs, images and volumes.

已驗證STDIO僅桌面雲端與基礎設施

概覽

Containerport 的本機 MCP 服務；無需登入；STDIO。

暫無 AI 概覽：以下資訊來自註冊中心條目和服務本身。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Containerport，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

containerport

containerport is a small MCP server and CLI for everyday Docker container work. It is a clean-room rebuild of a defined core subset of container operations — ten tools that map directly onto the Docker CLI: list, inspect, run, start, stop and remove containers, list and pull images, read container logs, and list volumes.

It is deliberately not Docker's MCP catalog/toolkit gateway. There is no compose support, no image building, no network or swarm management, no registry authentication, no exec-into-container, and no catalog/gateway tooling — just the container operations an agent reaches for most, executed honestly through the host's docker binary.

Every call is built as an argument array and run with execFile semantics — never a shell string — so image names, environment values and ports cannot be reinterpreted as shell syntax. A command passed to run-container runs through the container's own sh -c, not a host shell. The executor is injectable, which is how the test suite verifies the exact argument arrays with a fake.

The host needs a working docker CLI. When docker is absent, calls fail honestly with the underlying spawn error (ENOENT) instead of a fabricated result. The published container image bundles no docker binary: it expects a host executor (for example a mounted Docker socket workflow) and says so in its Dockerfile.

Install

bash
npx @reneturcios/containerport list-containers --alldocker run -i ghcr.io/cloudcorprecords/containerport

CLI

bash
containerport list-containers [--all]containerport inspect-container <container_id>containerport run-container <image> [--name n] [--port 8080:80] [--env KEY=val] [--command "echo hi"]containerport start-container <container_id>containerport stop-container <container_id>containerport remove-container <container_id> [--force]containerport list-imagescontainerport pull-image <image>containerport get-container-logs <container_id> [--tail 100]containerport list-volumescontainerport --version

Exit codes: 0 success, 1 docker error, 2 usage error.

MCP server

bash
npx -y @reneturcios/containerport mcp
json
{  "mcpServers": {    "containerport": {      "command": "npx",      "args": ["-y", "@reneturcios/containerport", "mcp"]    }  }}

Tools

ToolInputWhat it does
list_containersall (boolean, optional)docker ps [--all] --format json, parsed.
inspect_containercontainer_id (required)docker inspect, single document.
run_containerimage (required), name, ports[], env[], commanddocker run -d, returns the new container id.
start_containercontainer_id (required)docker start.
stop_containercontainer_id (required)docker stop.
remove_containercontainer_id (required), forcedocker rm [-f].
list_images—docker images --format json, parsed.
pull_imageimage (required)docker pull.
get_container_logscontainer_id (required), taildocker logs [--tail n].
list_volumes—docker volume ls, parsed driver/name pairs.

Executor failures — a missing docker binary, a daemon error, a nonexistent container — are reported as tool errors carrying the underlying message.

Development

bash
npm installnpm run buildnpm testnpm run dev

Tests run entirely on a fake executor: exact argument arrays, output parsing, and error propagation. No live Docker daemon is touched.

License

MIT — see LICENSE.

來源：README.md，提交 05aab94

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.0最新Nov 3, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分