Containerport

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

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

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

Containerport's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Containerport in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 05aab94

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts