Tapo MCP

MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents

io.github.mihai-dinculescu/tapo-mcp · Repository · version 0.5.0 · 788 stars · listed from registry

Install

The sweep pulls the image and runs it in a throwaway container, but this is the command a user would run:

docker run -i --rm ghcr.io/mihai-dinculescu/tapo-mcp:0.5.0

Needs credentials: TAPO_MCP_USERNAME, TAPO_MCP_PASSWORD, TAPO_MCP_DISCOVERY_TARGET. The probe used placeholder values, so an amber needs credentials result below means the server asked for the real ones, not that it is broken. Maintainers: how to go green.

Results by platform

Linux

needs credentials2026-08-16 · probed over oci

1 recorded run, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
Error: Refusing to start: TAPO_MCP_HTTP_ADDR binds to a non-loopback address (0.0.0.0:3000) with no TAPO_MCP_API_KEY set, exposing unauthenticated smart-home control to the network. Set TAPO_MCP_API_KEY to require bearer authentication, or bind to a loopback address.

macOS

not tested2026-08-16

1 recorded run, oldest first.

docker not available on this runner, so container distributions are probed on Linux only

Windows

not tested2026-08-16

1 recorded run, oldest first.

docker not available on this runner, so container distributions are probed on Linux only

Badge

Paste this into the project README to show the current result:

[![does it install](https://img.shields.io/endpoint?url=https://doesitinstall.com/badge/io.github.mihai-dinculescu__tapo-mcp.json)](https://doesitinstall.com/s/io.github.mihai-dinculescu__tapo-mcp.html)