GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Run core Docker container operations: list, run, inspect, logs, images and volumes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"containerport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/containerport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add containerport -- npx -y @reneturcios/containerport mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"containerport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/containerport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"containerport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/containerport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
npx @reneturcios/containerport list-containers --all
docker run -i ghcr.io/cloudcorprecords/containerport
containerport list-containers [--all]
containerport inspect-container containerport run-container [--name n] [--port 8080:80] [--env KEY=val] [--command "echo hi"] containerport start-container containerport stop-container containerport remove-container [--force] containerport list-images containerport pull-image containerport get-container-logs [--tail 100] containerport list-volumes containerport --version
Exit codes: 0 success, 1 docker error, 2 usage error.
npx -y @reneturcios/containerport mcp
{
"mcpServers": { "containerport": { "command": "npx", "args": ["-y", "@reneturcios/containerport", "mcp"] } } }
| Tool | Input | What it does |
|---|---|---|
list_containers | all (boolean, optional) | docker ps [--all] --format json, parsed. |
inspect_container | container_id (required) | docker inspect, single document. |
run_container | image (required), name, ports[], env[], command | docker run -d, returns the new container id. |
start_container | container_id (required) | docker start. |
stop_container | container_id (required) | docker stop. |
remove_container | container_id (required), force | docker rm [-f]. |
list_images | — | docker images --format json, parsed. |
pull_image | image (required) | docker pull. |
get_container_logs | container_id (required), tail | docker 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.
npm install
npm run build npm test npm run dev
Tests run entirely on a fake executor: exact argument arrays, output parsing, and error propagation. No live Docker daemon is touched.
MIT — see LICENSE.