tplink-deco-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECO_HOST | Yes | IP of the main Deco, such as 192.168.68.1 | |
| DECO_TIMEOUT | No | Seconds per router request | 10 |
| DECO_PASSWORD | Yes | The router's local admin password | |
| DECO_USERNAME | No | The router's username | admin |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_deco_nodesA | List the Deco units that form the mesh: the gateway and every satellite. Returns each unit's MAC, name, model, role ( |
| get_router_performanceA | Report how busy the gateway is and how much traffic flows through the mesh right now. Returns CPU and memory usage of the gateway in percent, the number of online clients and the summed instantaneous download and upload rates of every client, in kilobytes per second. |
| get_internet_statusA | Report whether the mesh is online and how the gateway reaches the provider. Returns the WAN cable state, the IPv4 and IPv6 connection state
( |
| get_wifi_configurationA | Describe the Wi-Fi networks the mesh broadcasts and how each radio is tuned. Returns every network ( |
| list_clientsA | List the devices (phones, computers, TVs, IoT gadgets) the mesh knows about. Returns each device's MAC, name, IP, whether it is online, the network
it joined ( |
| update_clientA | Rename a device and optionally change its category in the Deco app. The router only applies an edit that carries a name, so |
| remove_clientA | Forget a device that is no longer used, removing it from the client list. Meant for offline devices: the router lists the device again as soon
as it reconnects. This does not block it — use |
| list_blocked_clientsA | List the devices that are blocked from the internet across the whole mesh. Returns each blocked device's MAC, the name and the category stored with the block. |
| block_clientA | Block a device from the internet on every Deco unit; it stays on the local network.
|
| unblock_clientA | Restore internet access for a device on the blocklist. |
| list_address_reservationsA | List the fixed IPs the DHCP server always hands to the same device. Returns each reservation's MAC and IP with the device name the mesh
shows for that MAC ( |
| add_address_reservationA | Reserve a fixed IP for a device that has none yet. The device picks the address up on its next DHCP renewal or reconnect.
Use |
| update_address_reservationB | Move a device's existing fixed IP reservation to another address. |
| remove_address_reservationA | Drop a device's fixed IP reservation; it gets a dynamic address on its next renewal. |
| get_system_logA | Read one page of the router's system log, newest page by default. Returns up to 100 lines from oldest to newest (time, syslog facility
and level, the process that wrote it, message), the page count, and
the severities that can be passed as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
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.
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.
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.
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.