Skip to main content
Glama
thalisantunes

mcp-omada

by thalisantunes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-omada

No user-submitted related servers found.

    Related Servers

    • omada-mcp

      margosmark
      A
      license
      B
      quality
      B
      maintenance
      A read-only Model Context Protocol server that enables clients to inspect TP-Link Omada controller networks, including sites, devices, clients, VLANs, ACLs, NAT, mDNS, QoS, and DNS, without changing configuration by default.
      6
      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

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

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (list vs detail vs summary vs info), and get_clients/get_alerts are unambiguous. However list_devices and get_wifi_summary overlap on per-AP channel/radio data, so an agent could reasonably confuse them for WiFi-channel queries.

    Naming Consistency5/5

    All tool names use consistent snake_case verb_noun patterns: list_sites, list_devices, get_device_detail, get_wifi_summary, get_controller_info, get_clients, get_alerts, set_radio_channel. The verbs list/get/set are applied predictably.

    Tool Count5/5

    Eight tools is a well-scoped size for an Omada controller server: it covers sites, devices, clients, alerts, controller info, WiFi summaries, and one guarded write without feeling bloated or thin. Each tool maps to a distinct data need.

    Completeness3/5

    The read surface covers common monitoring needs but lacks broader management operations: no SSID/VLAN configuration, no client block/unblock, no device reboot, and no update/delete beyond a single radio-channel write. Notable gaps remain for a server named mcp-omada.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources