Tapo MCP

Rather than one tool per device family, devices advertise separate lists of set and get capabilities — OnOff, Brightness, Colour on the write side; device info, temperature and humidity history, hub trigger logs on the read side — so a single control_device tool covers a bulb, a plug and a power strip socket without the tool list growing with the shelf. Every stateful call runs check_device first, verifying that the device ID still matches the IP being addressed; on a DHCP network that check is what stops a reassigned address from being commanded by mistake. Cameras add a snapshot tool, and they need a camera account set in the Tapo app that is separate from the cloud login. Written in Rust on the rmcp SDK, served over streamable HTTP with an optional bearer token and a host allowlist. Unofficial.