
XenMCP Docker agent
com.xenmcpPublished by xenmcp.comv1.0.1Updated Nov 11, 2026
Read-only MCP server for one Docker host: containers, inspect, logs, stats, events. No exec.
The publisher's own server: Docker Recipes
Overview
Read-only MCP server for one Docker host: lets an assistant list and inspect containers, read logs, view live stats and recent events, with no exec or changes.
- What you can do
- Inspect the Docker host: version, OS, CPUs, memory, container and image counts
- List containers with name, image, state, uptime, ports and compose project
- Inspect a container's state, exit code, OOM kills, restarts, health check, limits, mounts and networks
- Read container logs by time window, stdout or stderr, with text or regex search, up to 500 lines per call
- Show current CPU, memory, network and process stats, and events from the last seven days
- When to use it
- Useful when you want an assistant to diagnose why a container is restarting, crashed or unhealthy, or to review logs and resource use on a single Docker host without giving it the ability to change anything.
- Requirements
- Runs as a container image next to your containers, with the Docker socket mounted read-only and a group added for socket access. Over HTTP it needs XENMCP_AGENT_KEY (at least 32 characters) sent as an Authorization Bearer header, plus a reverse proxy for HTTPS and XENMCP_ALLOW_IPS for allowed callers. A stdio mode needs no key or port.
Installation
In SourceWeft
- Open XenMCP Docker agent in the dashboard and add it to a workspace.
- 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
XenMCP Docker agent
A small, read-only MCP server for the containers on one Docker host. Run it next to your containers, put it behind your reverse proxy, and connect it to Claude, Cursor or VS Code through XenMCP: every person signs in on their own (OAuth), access can be revoked at any time, and every call is in the journal.
It can see, never change:
There is no tool that starts, stops, restarts, removes, execs, builds or pulls. The agent sends Docker only a short list of GET requests (lib.mjs, allowedPath) and refuses everything else before it leaves the process.
Install
- In the XenMCP panel: Add server → Docker agent. It shows a key and the command below with the key filled in.
- On your Docker host:
- Make it reachable over HTTPS through your reverse proxy (below), e.g.
https://docker-agent.example.com/mcp. - In the panel: enter that address and press Check and save.
Or with Docker Compose:
Reverse proxy
The agent listens on plain HTTP; your proxy adds HTTPS. It must pass X-Forwarded-For (all three below do).
Caddy
nginx
Traefik (labels on the agent container, without ports)
Without XenMCP
The agent is a plain MCP server (Streamable HTTP at /mcp), so any client that can send a header works. Set XENMCP_ALLOW_IPS to the addresses that may call it (* for any, only behind your own proxy or firewall) and send the key as Authorization: Bearer <key>. Without XenMCP there is no per-person sign-in and no journal: everyone with the key has the same access.
Over stdio, for a local client
Started with --stdio, the agent talks MCP over stdin/stdout instead of HTTP: no key, no port, no address list – whoever starts it already has the Docker socket. For Claude Desktop, Cursor or VS Code on the Docker host itself:
Or from a checkout: node server.mjs --stdio. The same six read-only tools; XENMCP_CONTAINERS and the xenmcp.hide label apply.
It is listed in the official MCP Registry as com.xenmcp/docker-agent (server.json in this repository).
Settings
Hide single containers with the label xenmcp.hide=true: they are left out of every answer.
Good to know
- Logs are what Docker keeps: with the default
json-filedriver everything since the container was created, unless you setmax-size/max-file. A recreated container starts with an empty log. For history beyond that, use Grafana + Loki. - Logs can contain personal data and secrets. What a tool returns goes to the AI client you connect (for Claude: Anthropic). Hide containers you do not want to share.
- The socket is mounted read-only, but Docker's API does not know read-only mounts — the limit is the agent's own allow-list, which is why it is small, open source and tested (
npm test,npm run e2e).
Develop
Questions and feedback
Ask in the XenMCP community on Discord (forum #help, tag docker-agent) or open an issue here. Security issues: [email protected], not in public.
Source: README.md at commit 6497612
Tools
0Version history
1- v1.0.1LatestNov 11, 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
Other Docker integrations
Docker Recipes
recipes.dockerOfficial publisher
A remote MCP server that lets an assistant search and fetch ready-to-run Docker Compose stacks for self-hosting and home labs.

Reverse Engineer Anything (Docker)
Published by GitHub account psyb0t
A Docker-packaged REA reverse-engineering server that lets an assistant decompile APKs, inspect binaries and drive Android devices over adb.

Docker Hub Mcp
Published by GitHub account mrfentmen
Looks up Docker Hub images, their tags and pull counts, so an assistant can check container images without an API key.

Docker Image Shape
Published by GitHub account sadri-dridi
Remote MCP server of small, mostly stateless utility checks: Docker image name shape, URL and hostname parsing, HTTP status probes, time, and arithmetic.

Docker
Published by GitHub account rog0x
Local MCP server that lets an assistant inspect Docker containers, images and logs, and review Dockerfiles and Compose files for best practices.