Skip to main content
Glama
gxxHuang
by gxxHuang

Related Servers

Alternatives to iKuai MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with iKuai routers, enabling Claude to query system status, manage devices, and configure router settings via natural language.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A comprehensive MCP server for network device management via SSH/Telnet. Supports multiple vendors such as Cisco IOS and BDCOM, enabling AI assistants to execute commands and manage routers, switches, and firewalls.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for comprehensive OPNsense firewall management, enabling AI assistants to manage firewall rules, NAT, VLANs, and network diagnostics, plus execute SSH/CLI commands. Supports safety modes like read-only and dry-run for safe operation.
      118 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to manage network infrastructure through the Equinix Fabric API, including ports, connections, and service profiles. It provides 22 tools for tasks like creating virtual connections, managing service tokens, and querying metro locations.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for UnoRouter, an OpenAI-compatible gateway with 200+ models, providing search_models, get_pricing, and chat tools to interact with various AI models through natural language.
      3
      87 npm
      AGPL 3.0

    TDQS

    C2.4/5.0

    Scored across 229 tools

    Disambiguation1/5

    With 229 tools, many have overlapping purposes such as multiple get/list monitoring tools (get_line_monitoring, get_terminal_list, get_load_monitoring) and numerous log retrieval functions. Duplicate tools like get_ddns_config and get_dynamic_dns_config further confuse selection, making it nearly impossible for an agent to reliably distinguish between them.

    Naming Consistency3/5

    The majority of tools follow a verb_noun pattern (list_*, get_*, add_*, delete_*, set_*, toggle_*), but the choice between get_ and list_ is inconsistent (list_wan_configs vs get_wan_status). Outliers like kick_pppoe_user, wake_on_lan, subnet_calculator, and change_admin_password deviate from the pattern, though overall naming remains readable.

    Tool Count1/5

    229 tools is drastically excessive for an MCP server. Even for a comprehensive router management system, this volume overwhelms agents and violates the principle of a well-scoped toolset, far exceeding the 3-15 tool sweet spot.

    Completeness4/5

    The toolset thoroughly covers router domains: interfaces, VPN, DHCP, DNS, routing, NAT, firewall, QoS, logs, and system utilities. However, many resources lack update/modify operations (e.g., VLAN, DHCP static bindings, IP groups), and the presence of duplicates suggests minor workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues