Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"docker-tools": {
"args": [
"D:/products/mcp-servers/mcp-docker-tools/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Docker container management and Dockerfile analysis
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
This server is missing a description.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
Enhanced MCP server for GitLab: group projects listing and activity tracking
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
MCP Security Weekly
Get CVE alerts and security updates for io.github.rog0x/docker and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Docker management tools for AI agents, built on the Model Context Protocol.
Provides five tools for inspecting containers, images, Dockerfiles, and Compose configurations — all accessible to LLMs through MCP.
| Tool | Description |
|---|---|
docker_container_list | List running or all containers with status, ports, image, created time, and resource usage (CPU, memory, network/block I/O) |
docker_image_list | List Docker images with size, tags, created date, and layer count |
docker_dockerfile_analyze | Analyze a Dockerfile for best practices: multi-stage builds, non-root user, layer caching, image size, security |
docker_compose_analyze | Analyze docker-compose.yml: services, ports, volumes, networks, health checks, dependencies, and improvement suggestions |
docker_container_logs | Get container logs with tail, keyword filter, time range, and timestamp support |
git clone <repo-url>
cd mcp-docker-tools
npm install
npm run build
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"docker-tools": {
"command": "node",
"args": ["D:/products/mcp-servers/mcp-docker-tools/dist/index.js"]
}
}
}
claude mcp add docker-tools node D:/products/mcp-servers/mcp-docker-tools/dist/index.js
Or add to .claude/settings.json:
{
"mcpServers": {
"docker-tools": {
"command": "node",
"args": ["D:/products/mcp-servers/mcp-docker-tools/dist/index.js"]
}
}
}
{ "tool": "docker_container_list" }
{ "tool": "docker_container_list", "args": { "all": true, "format": "table" } }
{ "tool": "docker_image_list", "args": { "filter": "node" } }
{
"tool": "docker_dockerfile_analyze",
"args": {
"content": "FROM node:20\nCOPY . .\nRUN npm install\nCMD [\"node\", \"index.js\"]"
}
}
{
"tool": "docker_compose_analyze",
"args": {
"content": "services:\n web:\n image: nginx\n ports:\n - 80:80"
}
}
{
"tool": "docker_container_logs",
"args": { "container": "my-app", "tail": 50, "filter": "error" }
}
MIT