tplink-deco-mcp-server
Allows managing and monitoring a TP-Link Deco mesh Wi-Fi network through local router tools: listing Deco nodes, checking router performance and internet status, viewing Wi-Fi configuration, listing/updating/removing clients, blocking/unblocking devices, and managing DHCP address reservations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tplink-deco-mcp-serverwhich devices are connected to my Deco mesh right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
tplink-deco-mcp-server
Model Context Protocol 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
SDK — no cloud account involved.
Tools
Tool | What it does |
| Deco units of the mesh: model, role, IP, firmware, internet status, backhaul signal. |
| Gateway CPU and memory usage, online clients and total traffic right now. |
| WAN cable, IPv4/IPv6 connection state, public address, gateway and DNS. |
| Every SSID (main, guest, IoT, MLO) with its bands, plus each radio's channel settings. Passwords only with |
| Devices known to the mesh: name, MAC, IP, network, band, category, current traffic. Filter: |
| Rename a device and optionally change its category. |
| Forget an offline device. |
| Devices blocked from the internet. |
| Cut a device off from the internet, or let it back in. |
| Fixed IPs reserved by the DHCP server, with the device names. |
| Reserve, move or release a device's fixed IP. |
Tools that change settings are annotated as such, so clients can ask for confirmation before running them.
Related MCP server: tplink-mcp
Install
pip install tplink-deco-mcp-serverRequires Python ≥ 3.14 and a Deco router reachable on the local network.
Configuration
The server reads the router credentials from environment variables:
Variable | Required | Default |
| yes | — (IP of the main Deco, such as |
| yes | — (the router's local admin password) |
| no |
|
| no |
|
The router keeps a single session per account. Every login — from this server, the Deco app or another integration — ends the previous one. The server logs in again by itself when its session is taken over, but the Deco app may ask you to log in again after the server has been used.
Use with Claude Desktop / Claude Code
{
"mcpServers": {
"deco": {
"command": "uvx",
"args": ["tplink-deco-mcp-server"],
"env": {
"DECO_HOST": "192.168.68.1",
"DECO_PASSWORD": "your-password"
}
}
}
}Run with Docker
A multi-arch image (linux/amd64, linux/arm64) is published to GitHub
Container Registry on every release, tagged with the release version
(1.2.0, 1.2, 1) and latest:
docker run -d --name deco-mcp \
-e DECO_HOST=192.168.68.1 \
-e DECO_PASSWORD=your-password \
-p 8000:8000 \
ghcr.io/roquerodrigo/tplink-deco-mcp-server:latestThe container serves
Streamable HTTP
at http://localhost:8000/mcp, with a health endpoint at /healthz:
{
"mcpServers": {
"deco": {
"type": "http",
"url": "http://localhost:8000/mcp"
}
}
}The HTTP endpoint has no authentication of its own: keep it on a trusted network or behind a reverse proxy that authenticates. To use stdio instead, run the server binary as the container command:
{
"mcpServers": {
"deco": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "DECO_HOST", "-e", "DECO_PASSWORD",
"ghcr.io/roquerodrigo/tplink-deco-mcp-server:latest",
"tplink-deco-mcp-server"
],
"env": {
"DECO_HOST": "192.168.68.1",
"DECO_PASSWORD": "your-password"
}
}
}
}Command-line options
tplink-deco-mcp-server [--transport {stdio,streamable-http}] [--host HOST] [--port PORT]
[--log-level {DEBUG,INFO,WARNING,ERROR}]stdio is the default transport. --host (default 127.0.0.1) and --port
(default 8000) apply to streamable-http.
Run from source
git clone https://github.com/roquerodrigo/tplink-deco-mcp-server.git
cd tplink-deco-mcp-server
uv sync
DECO_HOST=… DECO_PASSWORD=… uv run tplink-deco-mcp-serverSupport
This MCP server is built and maintained on personal time, on hardware bought for the purpose. If it is useful to you, consider sponsoring the work — it keeps the devices, the testing and the releases coming.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.
IP lookup with VPN/Tor/datacenter flags, batch lookup, WHOIS (RDAP), DNS, reverse DNS, subnet math.
Router default logins, compliance index, MAC/OUI lookup. Reads free; submit_correction is Pro.
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Ubiquiti UniFi network infrastructure for monitoring devices, managing clients, and performing configuration tasks like blocking/unblocking devices and viewing network health.101GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage TP-Link routers by listing clients, checking status, controlling Wi-Fi, and rebooting via natural language.2MIT
- AlicenseAqualityCmaintenanceLets 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.94MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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