Skip to main content
Glama
taroru5358

ax11000-mcp

by taroru5358
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ax11000-mcp

No user-submitted related servers found.

    Related Servers

    • tplink-mcp

      axo4xo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage TP-Link routers by listing clients, checking status, controlling Wi-Fi, and rebooting via natural language.
      2
      MIT

    • firewalla-mcp

      djuntgen
      A
      license
      B
      quality
      A
      maintenance
      Exposes the Firewalla MSP API as tools for Claude Code and other MCP clients, enabling natural-language management of Firewalla boxes, alarms, rules, devices, flows, target lists, and trends with full read/write capabilities.
      19
      MIT

    • omada-mcp

      kaviththiranga
      A
      license
      A
      quality
      C
      maintenance
      Lets an AI assistant inspect and adjust TP-Link Omada WiFi networks by searching, describing, and calling any of roughly 1,650 Omada Open API operations through nine tools. It is read-only by default, refusing every non-GET request unless writes are explicitly unlocked, and even then returning a dry-run preview until a change is confirmed.
      9
      4
      MIT

    • omada-mcp

      dfla-me
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to read and safely modify TP-Link Omada networks through capability-gated tools, with a default read-only profile and dry-run writes for security.
      11
      1
      MIT

    • TP-Link Router MCP Server

      consigcody94
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables automation and management of TP-Link BE3600 routers through browser automation, supporting port forwarding configuration, network status monitoring, and device management without reverse-engineering the router's encryption.
      1
      MIT
    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.1/5.0

    Scored across 16 tools

    Disambiguation4/5

    Tools target distinct resources: DHCP leases, reservations, connected devices, mesh nodes, and firmware/IP status are clearly separated, and read vs. write actions (add/delete/set/reboot) are explicit. The main ambiguity is raw_request, which can overlap with any specific read tool, but its escape-hatch role and confirm-gating for writes are clearly described.

    Naming Consistency4/5

    Names follow a mostly predictable snake_case verb_noun pattern (get_*, list_*, add_*, delete_*, set_*, reboot_*). Minor deviations like router_overview, session_info, and raw_request are readable and do not seriously undermine consistency.

    Tool Count4/5

    At 16 tools this is slightly above the typical 3–15 sweet spot, but each tool covers a distinct router management function: telemetry reads, DHCP reservations, Wi-Fi control, reboot, and raw access. There is little obvious filler, though raw_request is a broad catch-all that adds surface area.

    Completeness4/5

    Core read/write lifecycle for DHCP reservations and Wi-Fi on/off is covered, and raw_request provides an escape hatch for unsupported endpoints. Gaps remain for updating an existing reservation and for broader Wi-Fi SSID/password or security configuration, which agents would need to handle via raw_request.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources