Menu

I let my AI agent look after my NAS, but it can't reboot it: zima-mcp
📰

I let my AI agent look after my NAS, but it can't reboot it: zima-mcp

DEV Community: github·Christian Anderson·about 13 hours ago
#Pk5hKpIy
#devtogithub#technology#devto#dev#zima
Reading 0:00
15s threshold

My ZimaBlade runs 16 containers: Immich, a dashboard, Uptime Kuma, a reverse proxy and a few others. When something feels slow, the question is always the same one: is the box busy, and which container is it? I got fed up SSHing in to run docker stats , so my self-hosted agent has had a set of "Zima ops" tools for a while. Today I cleaned them up and published them as zima-mcp .

What it is

An MCP server. MCP is the plug that lets Claude Desktop, Claude Code, Cursor and other AI clients call tools. zima-mcp gives them seven:

zima_load : uptime and load average

zima_top : top processes by CPU

zima_docker_ps and zima_docker_stats : containers, and CPU/memory per container

zima_disk : df -h

zima_container_logs : the last N lines for one container

zima_restart_container : restart one container, only if it's on your allowlist

Every tool is one fixed command over plain SSH. Nothing gets installed on the Zima.

The bit I actually care about: what it can't do

ZimaOS is a bit odd.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.