omv-mcp
Related Servers
Alternatives to omv-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that lets AI assistants manage an OpenMediaVault NAS over SSH using OMV's own RPC interface, covering disks, filesystems, shares, users, S.M.A.R.T. health, services, and configuration changes. It exposes a small set of generic tools to discover and call RPC methods, plus optional shell access.6MIT
- FlicenseBqualityCmaintenanceEnables AI assistants to monitor and manage OpenMediaVault NAS systems by providing access to storage, network shares, user accounts, and system services. It supports OMV 5 and 6 via the JSON-RPC API for comprehensive hardware and configuration oversight through natural language.392-
- AlicenseAqualityCmaintenanceExposes a Raspberry Pi homelab's systemd service health, disk usage, CPU temperature, and LAN game-server status as read-only MCP tools, letting MCP clients answer questions like "how's the homelab doing?" without SSHing in manually.4MIT
- AlicenseNot gradedqualityBmaintenanceRemote Linux operations via SSH, exposed as an MCP server, with tools for filesystem, systemd, Docker, network, and more, using per-user AD authentication and optional sudo elevation.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP-capable agent to operate a heterogeneous cluster of Debian/Armbian Linux nodes over SSH from a single inventory, inspecting status and logs, managing packages, services, files, storage and NFS, and deploying new capabilities to nodes through installable modules. Built-in cluster tools fan out to nodes by explicit names, roles or tags with bounded concurrency, while modules can be installed on compatible nodes and run on demand or as systemd services.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for Raspberry Pi exposing tools for host health checks, shell execution, and Docker container restarts over authenticated HTTP.1-
TDQS
Scored across 48 tools
Most tools have clearly distinct purposes, but smart_status vs smart_health and disk_usage vs storage_summary overlap enough to cause confusion. Overall, an agent can usually tell tools apart with careful reading.
Naming follows a loose pattern: list_* for enumeration and verb_object for actions, but there are outliers like docker_system_df, omv_rpc, cpu_temp, and container_stats. Mixed conventions are still readable but not consistently applied.
48 tools is far beyond the typical 3-15 range and the 25+ threshold. The high granularity (e.g., six SMART-specific tools) feels excessive, especially since generic run_command and omv_rpc already exist for arbitrary operations.
The tool set covers monitoring and lifecycle operations for Docker/stacks and system info, but lacks CRUD for OMV shared folders, users, groups, and SMB shares. The unrestricted omv_rpc and run_command fill gaps but bypass the safer specific tools.