Skip to main content
Glama
jooservices

vigor3912s-mcp

by jooservices
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vigor3912s-mcp

No user-submitted related servers found.

    Related Servers

    • AsusWRT MCP Server

      teefloo
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to monitor and securely manage AsusWRT and AsusWRT-Merlin routers via SSH with allowlisted commands, supporting read-only monitoring and controlled mutations.
      47
      2
      MIT

    • Keenetic NOC MCP

      Spiceman161
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to perform controlled diagnostics and configuration of Keenetic and Netcraze routers over LAN RCI or remote KeenDNS HTTPS, with read-only mode, guarded writes, and centralized secret masking.
      19
      MIT

    • mtik-mcp

      ardianryan
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to audit, inspect, and safely configure MikroTik RouterOS v7 routers through tools for connection testing, system status, security audits, firewall mangle management, routing, DHCP leases, sanitized exports, containers, and adlist queries.
      26 npm
      1
      GPL 3.0

    • io.github.jeff

      halid9
      A
      license
      Not graded
      quality
      B
      maintenance
      Bridges AI assistants with MikroTik RouterOS devices, enabling natural language management of network configurations, firewall, VLANs, VPNs, and diagnostics via ~300 tools.
      1
      MIT

    • tailscale-mesh-mcp

      R-zin
      F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to discover devices and perform connectivity diagnostics across a private Tailscale or WireGuard mesh through authenticated CLI or REST API backends. Supports safe dry-run simulations before affecting live node state.
      2
      -
    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 217 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as show_traffic, show_clienttraffic, show_statistic, sys_app_statistic, and sys_app_bandwidth all providing traffic/statistics views. Similarly, multiple status/info tools (show_status, sys_info, sys_health, sys_dashboard) blur boundaries, and several switch management tools (swm_show, swm_get, swm_query-like) are hard to distinguish.

    Naming Consistency3/5

    The naming is mostly verb_noun with prefixes like show_, sys_, wan_, dhcp_, but there is inconsistency: some use show_ (show_traffic), some use status (dhcp_status, linux_status, port_sniff_status), some use view (dos_view, internet_view, nat_view), and some use mixed forms like sys_dnsCacheTbl, sys_fr_log, and portmaptime_list. The pattern is readable but not uniform.

    Tool Count1/5

    217 tools is an extreme number for an MCP server, far beyond the typical well-scoped range. Even for a comprehensive router management interface, this creates overwhelming selection complexity and suggests the server exposes nearly every CLI command as a separate tool rather than a curated API.

    Completeness4/5

    The tool surface is extremely comprehensive, covering nearly every router subsystem: WAN, LAN, DHCP, NAT, VPN, QoS, firewall, VLAN, switch, AP management, IPv6, logging, and more. There are minor gaps (e.g., no explicit firmware upgrade tool beyond TFTP enable, no direct NAT rule creation tool), but the breadth is impressive and most workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources