Skip to main content
Glama
gxxHuang

iKuai MCP Server

by gxxHuang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to iKuai MCP Server

No user-submitted related servers found.

    Related Servers

    • ikuai-mcp

      beck-8
      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

    • Device MCP Server

      rajib884
      A
      license
      A
      quality
      D
      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

    • OPNsense MCP Server

      smaniktahla
      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.
      101 npm
      MIT

    • Equinix Fabric MCP

      sliuuu
      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

    • unorouter-mcp

      unorouter
      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
      82 npm
      AGPL 3.0
    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

    C2.4/5.0

    Scored across 248 tools

    Disambiguation3/5

    Individual descriptions are unusually detailed and often steer the agent correctly, but real overlaps remain: get_ddns_config and get_dynamic_dns_config appear to be the same resource, get_notifications/get_messages/list_realtime_notices/list_periodic_notices all retrieve '消息通知', get_wifi_all_settings duplicates get_wifi_basic_settings + get_wifi_advanced_settings, and several channel-scan tools (scan_surrounding_channels/start_channel_scan/get_channel_scan_status/scan_nearby_signals) blur together. With 248 tools, some boundaries are genuinely hard to distinguish.

    Naming Consistency4/5

    The vast majority follow a predictable verb_noun snake_case pattern (get_*, list_*, add_*, delete_*, set_*, toggle_*, enable_*, start_*/stop_*). Minor deviations exist (traceroute, subnet_calculator, ping_result, wake_on_lan, reboot_router), but they are isolated and still readable.

    Tool Count1/5

    248 tools is an extreme mismatch in scale; navigating this surface is a serious burden even for a complex router domain. Many clusters (dozens of read-only list_* and get_*_config) suggest granularity could be collapsed, and the calibration marks 50+ as the extreme end.

    Completeness4/5

    Coverage is remarkably broad across WAN/LAN, VLAN, DHCP, VPN, firewall/ACL, wifi, firmware, logs, and monitoring, with full CRUD on many domains. However, a large number of list_* tools (load balance, protocol/port/domain forwarding, groups, time plans, NAT, wireless VLANs) have no corresponding add/update/delete, and update/edit operations are generally sparse, leaving notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources