tolpo MCP server

Local-first control of TP-Link Tapo smart-home devices for AI agents.

tolpo turns the Tapo devices on your network into a single interface that an AI agent, or your own code, can read and control. It talks to each device directly over the LAN through the open source python-kasa library, so no request ever leaves your home and no vendor cloud sits in the path. The only credential it needs is the Tapo account the devices already belong to.

It ships two interfaces over the same core:

is any door open?).

• An MCP server that assistants such as Claude use as tools (turn off the office lights,

• An HTTP API with an OpenAPI description at /docs, for scripts and dashboards.

The aim is that everything the Tapo app can do on your network can also be done by the agent: lights, plugs, hubs and their sensors, cameras, doorbells, robot vacuums, schedules, firmware, rooms, pairing, and even what the devices say to the internet. That is a lot of power, so every action has a level, and only the first levels are on until you raise them. See What an agent can do and the Security model.

Features

can be changed.

• Lights, plugs, the H100/H200 hub and its sensors, cameras and the doorbell, each with live state and a list of what

remembers which kinds of device it found in earlier runs, and an area for a kind you have never had stays off.

• The parts of the Tapo app are split into areas, such as lights, plugs, cameras, doorbells and the network. tolpo

security changes and things that are hard to undo, such as pairing or a factory reset, stay off until you raise the level, and the last two kinds also need a confirmation phrase on every call. Wi-Fi names, setup codes, passwords and tokens are never returned.

• Every action has a level from 0 to 4. Reading and reversible control (power, brightness, color) are on. Settings,

same video channel the Tapo app uses. No extra camera account is needed.

• A camera you name in the config gives an agent a still picture, a short run of pictures or a saved clip, through the

that are slow to wake. When a device cannot be reached, the answer says which one and why.

• Discovery combines a broadcast with a direct per-address sweep, remembers devices between runs and retries the ones

• State is cached briefly and device names resolve at once, so an agent is not blocked on a slow hub.
• A full test suite runs against simulated devices, so it needs no hardware.

Supported devices

tolpo works with whatever python-kasa can talk to, so the list is longer than the hardware we own. The table keeps two things apart: what we have run against real devices, and what python-kasa documents as supported but we have not tried.

Shortened. The full README is on GitHub.