hostpanel
Provides tools for interacting with a local Docker daemon, including retrieving daemon information and version, listing and inspecting containers with filters, and listing Docker Compose projects.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
hostpanel
hostpanel looks after a single host: Docker daemon and container
state, Compose projects, basic host information, file search, ZFS
pools, and journal logs. It exposes all of that through two
action-router tools, flux and scout, and the same two routers
on the command line. One binary serves both faces.
This is a labelled core subset of a larger documented surface. The implemented actions are listed below; every other documented action is omitted from this subset and is named in the build report and in the spec fixture, not silently dropped.
Only the local host is served. A host parameter, when supplied,
must be local; remote SSH targets are not part of this subset.
Processes are started with an argument array only — no command
string ever goes through a shell.
Install
npx @reneturcios/hostpanel helpOr run the container image:
docker run -i ghcr.io/cloudcorprecords/hostpanelThe container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead, and mount the Docker socket if you want the flux actions to reach a real daemon.
Related MCP server: Enterprise Infrastructure & Metrics MCP Server
CLI
hostpanel flux docker info
hostpanel flux docker version
hostpanel flux container list --params '{"state":"running"}'
hostpanel flux container inspect --params '{"container_id":"abc123"}'
hostpanel flux host info
hostpanel flux compose list
hostpanel scout nodes
hostpanel scout exec --params '{"command":"hostname"}'
hostpanel scout exec --params '{"command":"cat","args":["/etc/hostname"]}'
hostpanel scout find --params '{"path":"/srv","pattern":"*.log","limit":20}'
hostpanel scout zfs pools
hostpanel scout logs journal --params '{"unit":"docker","lines":50}'
hostpanel help
hostpanel --versionSuccessful calls print a JSON object with the argv that ran and
its captured stdout, stderr, and exitCode; nodes and the
help actions print their local answers directly. Exit codes:
0 on success, 1 when a call fails (including a refused
command or a non-zero child exit), 2 for usage errors.
MCP server
npx -y @reneturcios/hostpanel mcpMCP client configuration:
{
"mcpServers": {
"hostpanel": {
"command": "npx",
"args": ["-y", "@reneturcios/hostpanel", "mcp"]
}
}
}Tools
Both tools take a required action, an optional subaction, and
an optional params object. Parameter names inside params
follow the original per-action tables (host, container_id,
state, name_filter, image_filter, label_filter, path,
pattern, depth, limit, command, args, pool, lines,
unit, priority, since, until, grep).
Tool | Action | Subaction | What it does |
|
|
| Docker daemon information ( |
|
|
| Docker version ( |
|
|
| List containers ( |
|
|
| Inspect one container ( |
|
|
| OS, kernel, and architecture ( |
|
|
| List Compose projects ( |
|
| — | The flux action reference, answered locally. |
|
| — | The configured hosts: just |
|
| — | Run one allowlisted read command; requires |
|
| — | Find files by glob ( |
|
|
| List ZFS pools ( |
|
|
| Read the systemd journal ( |
|
| — | The scout action reference, answered locally. |
The exec allowlist
scout exec runs read-only inspection commands only. The full
allowlist is 18 commands: cat, head, tail, grep, rg,
ls, tree, wc, uniq, diff, stat, file, du, df,
pwd, hostname, uptime, and whoami. Anything else —
including git, shells, interpreters, and mutating tools — is
refused before any process starts. The command must be a single
name; arguments travel separately in the args array and are
passed as argv, never interpolated into a shell string.
Development
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, fake executor only
npm run dev # run the CLI from source via tsxTests inject a fake executor, so the suite records the argv each action would run and proves refused commands never reach the executor. No Docker daemon, ZFS pool, or journal is needed — and no live host result is claimed by the test suite.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Linux server administration over OAuth MCP: shell, Docker, systemd, files and monitoring.
Audit, pin and diff agent tool lists; preflight and watch remote MCP servers. Free tier; x402.
Read-only Linux server and Docker monitoring for AI assistants: CPU, memory, disk, network.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only observability of a Linux host via MCP, exposing allowlisted systemd, docker, nginx, logs, disk, and cert info without shell access.MIT
- AlicenseAqualityDmaintenanceProvides read-only access to host system metrics (CPU, memory, disk), Docker container health/logs, and sandboxed log file analysis via MCP tools, enabling AI agents to monitor enterprise infrastructure safely.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables inspecting, orchestrating, and troubleshooting Docker Engine and Docker Compose environments through six consolidated high-leverage MCP tools.9,656 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to safely monitor Linux VPS health, inspect Docker containers, retrieve service logs, and execute whitelisted recovery actions via MCP.31158 npm93 PyPIMIT