Skip to main content
Glama
Sign In
Homelab

Homelab

by seayniclabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Homelab

No user-submitted related servers found.

    Related Servers

    • npm-mcp

      omichelbraga
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables conversational management of Nginx Proxy Manager, including reverse-proxy routing, TLS certificates, access lists, and stream forwards, with built-in safety guardrails for production use.
      1
      MIT

    • npm-mcp

      wadew
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Nginx Proxy Manager instances through natural language, covering 28 tools for proxy hosts, certificates, streams, and more.
      17 PyPI
      MIT

    • master-mcp

      Raindancer118
      F
      license
      A
      quality
      C
      maintenance
      Enables unified administrative control over Cloudflare, Porkbun, Docker, Proxmox VE, Nginx Proxy Manager/NPMPlus, Uptime Kuma, Authentik, and Coolify. Exposes service discovery and action execution through three MCP tools with roughly 150 cataloged operations for managing DNS, containers, VMs, proxies, monitors, users, and related infrastructure.
      3
      -
    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 16 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action: Docker container/image/inventory tools, proxy resource tools, DNS zone/record tools, and diagnostic/overview tools. The main overlap is between high-level composite tools (expose_service, teardown_service, service_status, infrastructure_overview) and the lower-level resource tools, which can require judgment about which abstraction to use.

    Naming Consistency3/5

    All names use snake_case, but the convention is mixed: some are plural resource nouns (proxy_hosts, docker_containers, dns_records), some are module/status nouns (homelab_modules, homelab_health, service_status), and some are verb_noun action tools (diagnose_service, expose_service, teardown_service). The names are readable, but there is no single predictable pattern.

    Tool Count4/5

    Sixteen tools is reasonable for a homelab management server spanning Docker, reverse proxy, DNS, diagnostics, and service lifecycle. The count is slightly high because composite tools coexist with granular resource tools, but each tool still has a plausible role.

    Completeness4/5

    The surface covers core homelab workflows well: Docker inspection and lifecycle, proxy hosts/redirections/certificates/access lists, DNS zones/records, diagnostics, exposure/teardown, and status overview. Some gaps remain, such as management operations for tunnels, Authentik, uptime monitoring, and Docker volumes/networks beyond read-only inventory.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources