Skip to main content
Glama

Related Servers

Alternatives to genieacs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A high-performance Go-based MCP server that provides a microservice architecture for orchestrating diverse tools through gRPC and HTTP/REST APIs. Enables seamless integration of language-agnostic tools including ML capabilities, web search, calculations, and human interaction for intelligent agent workflows.
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provider-agnostic MCP server for managing heterogeneous infrastructure (SSH, Proxmox VE, Virtualizor, Hetzner Cloud, Cloudflare) via a JSON inventory, exposing tools for VM/container management, DNS, firewalls, and SSH operations.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Keenetic routers that runs on the router itself via Entware: clients, DHCP, Wi-Fi, VPN, logs, port forwarding and DNS records, with dry-run by default on every write. A background watcher calls out from the router when a log or config rule matches.
      49
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP platform that exposes each configured backend as its own OAuth-protected MCP endpoint, with browser-based configuration, per-account version pinning, and plugin backends such as MikroTik RouterOS and a generic MCP proxy.
      MIT

    TDQS

    A4.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action, and subtle pairs are explicitly separated: get_parameter (cached) vs refresh_parameter (fresh from device), delete_task vs retry_task, manage_preset vs manage_provision. Several tools queue tasks, but their purposes (reboot, download firmware, set/refresh parameters) are clearly different, and connection_request is explicitly documented as queueing nothing.

    Naming Consistency4/5

    Eleven of twelve tools follow a clean verb_noun snake_case pattern (get_parameter, set_parameter, delete_task, reboot_device, tag_device, search_devices, etc.). The outlier is connection_request, which drops the leading verb; manage_preset/manage_provision also fold create/update/delete into an action parameter rather than separate names, a minor inconsistency.

    Tool Count5/5

    Twelve tools is well within the ideal range and each earns its place: device discovery, parameter read/write/refresh, task lifecycle, firmware, presets, provisions, tagging, and connection requests. Nothing feels redundant or missing for the apparent ACS-management scope.

    Completeness4/5

    The surface covers the core TR-069 lifecycle: discover/tag devices, read/write/refresh parameters, reboot, download firmware, manage tasks (delete/retry), and CRUD presets/provisions. Minor gaps remain—no tool to list or upload the files that download_firmware references, and no dedicated task/fault listing tool (deferred to resource URIs), which agents can partly work around.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues