Skip to main content
Glama
ebenezer-isaac

tplink-easysmart-mcp

by ebenezer-isaac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tplink-easysmart-mcp

No user-submitted related servers found.

    Related Servers

    • vigi-nvr-mcp

      ebenezer-isaac
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents and MCP clients to talk directly to a local TP-Link VIGI NVR over its JSON API, reading device, camera, storage, and recording data, managing channels, and exporting footage as clips or snapshots over RTSP. Every mutating action is double-gated and dry-runnable, and authentication is engineered around the NVR's account-lockout so an agent cannot lock you out of your own recordings.
      45
      MIT

    • archer-router-mcp

      ebenezer-isaac
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM/MCP clients to read and, when explicitly allowed, modify TP-Link Archer AX53 router settings directly over the LAN using the router's own web protocol, without a browser or cloud account. It is read-first, write-gated, and lockout-aware, with tools for clients, DHCP, Wi-Fi, access control, presence history, and other router operations.
      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
    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.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, but switch_status and switch_check_auth both perform a credential-free probe and report session/auth/breaker state, creating one confusing pair. switch_login and switch_get_system_info also overlap in session handling, though their descriptions clarify the difference.

    Naming Consistency5/5

    All tools use snake_case with a consistent switch_ prefix. Verbs like get_, set_, resolve_, check_, login, and logout are conventional and readable throughout, with no mixed conventions.

    Tool Count5/5

    The 13 tools are well-scoped for a switch management server. They cover status, authentication, read operations, safe writes, a helper, and a specialized PoE cycle without excessive bloat.

    Completeness3/5

    The surface covers read-heavy diagnostics and limited safe mutations, but it lacks VLAN configuration, port speed/flow-control changes, LAG management, and a way to clear the auth breaker. These are notable gaps for full switch management, though core read and safe write workflows exist.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources