Skip to main content
Glama
tplink-deco-mcp-server

tplink-deco-mcp-server

by roquerodrigo

Related Servers

Alternatives to tplink-deco-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Lets Claude or any MCP client inspect a TP-Link Deco mesh locally — nodes, backhaul, clients, WAN, firmware — and carefully change settings with graded, read-back-verified writes, secrets redacted by default and an optional read-only mode. No cloud or app involved.
      8
      54 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Xiaomi/Redmi routers, providing read-only queries and management capabilities such as device listing, port forwarding, DHCP reservations, and reboot control.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants and terminal users to inspect and administer TP-Link routers through typed MCP tools, including live LTE signal and cell/band control, connected clients and DHCP reservations, Wi-Fi and LED settings, diagnostics, SMS/USSD, and guarded disruptive actions.
      39
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and other MCP clients to inspect and manage a TP-Link router over stdio, including device lists, DHCP leases and reservations, Wi-Fi settings, firmware and IP status, mesh nodes, and safe raw endpoint requests with confirmation for writes and secret masking.
      16
      MIT

    TDQS

    A4.1/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair: logs, mesh nodes, performance, WAN status, Wi-Fi config, clients, blocklist, and DHCP reservations never overlap. The few potentially confusable pairs (remove_client vs. block_client, add vs. update_address_reservation) are explicitly disambiguated in the descriptions, and the three diagnostic getters return clearly different data.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (get_, list_, update_, add_, remove_, block_, unblock_) with resource names that match across families (client, address_reservation, blocked_clients). No mixed conventions or vague verbs.

    Tool Count5/5

    15 tools sit at the top of the well-scoped range and each earns its place, since the read-only diagnostics, client management, blocklist, and reservation CRUD families are all genuinely distinct capabilities. Nothing feels padded or redundant.

    Completeness4/5

    Client, blocklist, and address-reservation lifecycles are fully covered (list/add/update/remove), and diagnostics span logs, WAN, performance, and Wi-Fi. Gaps remain: Wi-Fi configuration is read-only (no set/update for SSID or password) and there is no reboot or firmware operation, which are common requests for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues