Skip to main content
Glama
Sign In
Safe Omada MCP

Safe Omada MCP

by mariomsamy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Safe 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

    • omada-mcp

      shamalawy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access every TP-Link Omada Open API operation through generated tools for searching, inspecting, and invoking controller operations such as sites, devices, clients, wireless, VPN, firewall, and hotspot management.
      MIT

    • WhiteOmadaMcp

      ricardo-david-francisco
      A
      license
      B
      quality
      C
      maintenance
      Enables an AI assistant to answer plain-language questions about a TP-Link Omada network — why Wi-Fi drops, which switch port a device is on, which VLAN it uses, and whether radar or interference is at play — by reading switches, access points, SSIDs, clients, topology and logs through 59 tools. It stays read-only unless two separate gates are opened, and any change is dry-run first, then read back and diffed.
      59
      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

    C2.7/5.0

    Scored across 113 tools

    Disambiguation2/5

    Many tools have overlapping purposes: listDevices, getAllDeviceBySite, listDevicesStats, and searchDevices all return device inventories; getGatewayWanStatus, getGatewayLanStatus, and getGatewayPorts overlap heavily; cable-test tools and numerous AP config getters are hard to distinguish without reading full descriptions. Composite tools like getNetworkHealthSummary and getGatewayHealth help, but the set still presents multiple plausible choices for the same question.

    Naming Consistency3/5

    All names are camelCase, but conventions vary: getApDetail vs getSitesApsIpSetting vs getGridClientHistory vs listSitesCableTestSwitchesPorts mix resource-first and path-derived naming. Verbs are mostly get/list/search/diagnose, though the same resource can be addressed through different prefixes, making the pattern only partially predictable.

    Tool Count1/5

    113 tools is an extreme mismatch for a coherent MCP surface. The set is a broad mirror of controller endpoints rather than a curated set of operations, and many near-duplicate read endpoints make it difficult for an agent to choose correctly.

    Completeness2/5

    Coverage is heavily read-only: there are extensive getters for devices, clients, APs, switches, gateways, and firewall settings, but almost no create/update/delete operations for core lifecycle tasks such as adopting devices, upgrading firmware, configuring SSIDs, or editing ACLs. The searchOperations/describeOperation pair helps discovery but does not fill the missing mutation surface.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources