MCP server exposing TP-Link Deco mesh routers (nodes, clients, Wi-Fi, blocklist, fixed IPs) as tools for LLM clients
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tplink-deco-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# tplink-deco-mcp-server [](https://github.com/roquerodrigo/tplink-deco-mcp-server/actions/workflows/ci.yml) [](https://pypi.org/project/tplink-deco-mcp-server/) [](https://github.com/sponsors/roquerodrigo) [Model Context Protocol](https://modelcontextprotocol.io) server that exposes a **TP-Link Deco** mesh Wi-Fi network as tools an LLM client (Claude Desktop, Claude Code, etc.) can call. It talks to the router on your local network through the [`tplink-deco-api`](https://github.com/roquerodrigo/tplink-deco-api) SDK — no cloud account involved. ## Tools | Tool | What it does | | --- | --- | | `list_deco_nodes` | Deco units of the mesh: model, role, IP, firmware, internet status, backhaul signal. | | `get_router_performance` | Gateway CPU and memory usage, online clients and total traffic right now. | | `get_internet_status` | WAN cable, IPv4/IPv6 connection state, public address, gateway and DNS. | | `get_wifi_configuration` | Every SSID (main, guest, IoT, MLO) with its bands, plus each radio's channel settings. Passwords only with `include_passwords: true`. | | `list_clients` | Devices known to the mesh: name, MAC, IP, network, band, category, current traffic. Filter: `online_only`. | | `update_client` | Rename a device and optionally change its category. | | `remove_client` | Forget an offline device. | | `list_blocked_clients` | Devices blocked from the internet. | | `block_client` / `unblock_client` | Cut a device off from the internet, or let it back in. | | `list_address_reservations` | Fixed IPs reserved by the DHCP server, with the device names. | | `add_address_reservation` / `update_address_reservation` / `remove_address_reservation` | Reserve, move or release a device's fixed …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.