
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.
概览
Containerport 的本地 MCP 服务;无需登录;STDIO。
暂无 AI 概览:以下信息来自注册中心条目和服务本身。
安装
在 SourceWeft 中
- 打开 控制台中的 Containerport,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
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
CLI
Exit codes: 0 success, 1 docker error, 2 usage error.
MCP server
Tools
Executor failures — a missing docker binary, a daemon error, a nonexistent container — are reported as tool errors carrying the underlying message.
Development
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版本历史
1- v0.1.0最新Nov 3, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分