Skip to main content
Glama
irfanfath123

homelab-monitor-mcp

by irfanfath123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to homelab-monitor-mcp

No user-submitted related servers found.

    Related Servers

    • MemoryOS VPS Guardian

      AndersonVitaease
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to monitor server health and capacity, diagnose outages, inspect Docker and deployment status, and perform safe, bounded recovery actions via MCP without granting unrestricted shell or SSH access.
      10
      1
      Apache 2.0

    • Simple SSH MCP Server

      bhayanak
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants full SSH/SFTP remote operations — session management, command execution, interactive shells, file transfers, port forwarding, and system diagnostics.
      2
      MIT

    • srv-explore

      redmadrobot-rnd
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely explore and diagnose remote servers by providing a read-only sandbox with controlled access to files, logs, Docker, and databases. It exposes MCP tools that allow natural-language investigation and direct command execution without write permissions.
      3
      -

    • SSH MCP Server

      fionarchl
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible AI clients to remotely manage a Linux server via SSH, supporting file operations, Docker control, Git pulls, and arbitrary command execution.
      5,023 npm
      MIT

    • vpsdoctor-mcp

      miguelmartt
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to securely monitor and manage a self-hosted Linux VPS over SSH, including service status, disk and RAM usage, TLS certificate expiry, fail2ban summaries, and two-step confirmed service restarts or IP unbans.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Tools target mostly distinct resources (system, services, ports, disk, Docker, files, commands, DB), so an agent can usually pick correctly. The only real overlap is system_info and disk_detail, which both report disk usage, though disk_detail is clearly deeper.

    Naming Consistency3/5

    Names mix noun_noun (system_info, docker_ps, db_query), verb_noun (list_dir, read_file, edit_file), and noun_verb (docker_restart). The docker_ prefix groups Docker tools, but the overall set lacks a predictable verb pattern even though all names are snake_case.

    Tool Count4/5

    14 tools is within a reasonable range for a homelab monitor/manager and covers several domains without excessive duplication. It is slightly heavy, but nearly every tool appears to earn its place.

    Completeness3/5

    Monitoring coverage is strong, but lifecycle gaps exist: services only have status (no start/stop/restart), Docker only has restart (no stop/start), file operations lack create/delete, and list_hosts has no companion tools to act on remote hosts. These gaps will force agents to rely on run_command for common management tasks, which is explicitly restricted.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources