Skip to main content
Glama
MiguelTVMS

tplink-omada-mcp

by MiguelTVMS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to tplink-omada-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • tplink-omada-mcp

      aljopro
      A
      license
      C
      quality
      B
      maintenance
      MCP server that lets AI assistants monitor and manage TP-Link Omada controllers. It provides analytics and read-only queries plus write operations such as rebooting devices, blocking clients, and changing network or firewall settings.
      84
      MIT

    • Omada MCP Server

      Zesty0wl
      A
      license
      C
      quality
      B
      maintenance
      Enables managing TP-Link Omada SDN controllers through MCP, exposing 72 tools for sites, devices, clients, networks, switch ports, firewalls, schedules, and site settings, including reboot and PoE scheduling.
      72
      1
      MIT

    • UniFi Network MCP Server

      Ruashots
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage UniFi network infrastructure through 50+ tools covering devices, clients, networks, WiFi, firewall rules, and guest access using the official UniFi Network API.
      52
      74 npm
      5
      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

    C2.9/5.0

    Scored across 84 tools

    Disambiguation3/5

    Many tools have similar names (e.g., getApDetail vs getApGeneralConfig, getApRadios vs getRadiosConfig), but descriptions clarify differences. However, the sheer number of specific tools (e.g., 12 getSitesAps* tools) increases chance of misselection.

    Naming Consistency4/5

    Predominantly uses snake_case with verb_noun pattern (get_, list_). Minor inconsistencies like getClientsDistribution vs getClientDetail, and long names like getSitesHealthGatewaysWansDetails, but overall predictable.

    Tool Count2/5

    84 tools is excessive for most use cases. While the domain is broad, many tools could be consolidated (e.g., cable test logs vs full results). Presence of deprecated tools further inflates count.

    Completeness2/5

    Tool set is heavily read-oriented (get/list) with few mutation tools (missing triggerRfScan/triggerSpeedTest from provided list). Lacks create/update/delete for most resources, leaving agents unable to perform basic network management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources