# Tapo MCP

Controls TP-Link Tapo smart home hardware through the Model Context Protocol. Lets AI agents switch plugs, tweak lighting, query sensors, and grab camera frames.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed · ★ 863
- Author: mihai-dinculescu
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/mihai-dinculescu/tapo/tree/HEAD/tapo-mcp
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/tapo-mcp

## What it does

Built in Rust using the `tapo` crate and the `rmcp` SDK, the server runs as an HTTP service with Streamable HTTP transport on `127.0.0.1:3000`. It exposes local network hardware to AI agents through structured tools. Discovered hardware also maps to the `tapo://devices` resource in JSON format.

Supported actions include toggling power, setting light brightness, and picking color presets. For energy monitoring plugs such as P110 or P115, agents can inspect power draw history across hours, days, or months. Temperature and humidity records from T310 and T315 sensors cover the previous 24 hours. Hub sensor event logs are also readable.

Without `TAPO_MCP_USERNAME`, `TAPO_MCP_PASSWORD`, and a valid subnet target in `TAPO_MCP_DISCOVERY_TARGET`, the server cannot start. Capturing camera stills through `take_snapshot` requires dedicated camera credentials in `TAPO_MCP_CAMERA_USERNAME` and `TAPO_MCP_CAMERA_PASSWORD`.

## Requirements
- Needs: Docker
- Environment variables: `TAPO_MCP_USERNAME`, `TAPO_MCP_PASSWORD`, `TAPO_MCP_DISCOVERY_TARGET`, `TAPO_MCP_API_KEY`, `TAPO_MCP_DISCOVERY_TIMEOUT`, `OTEL_EXPORTER_OTLP_ENDPOINT` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Install**
- The MCP registry has no launch command for it: see the repository README

## When to use it
- toggle Tapo smart plugs and lighting fixtures via chat
- query historical energy consumption metrics from P110 and P115 plugs
- retrieve 24-hour temperature and humidity logs from T310 sensors
- capture JPEG still images directly from Tapo security cameras
- audit trigger event logs from smart buttons and motion sensors

## Example prompts
- List all Tapo smart devices discovered on my local network.
- Turn off the office light and set the bedroom lamp brightness to 50%.
- Check the power draw of the TV plug over the last 6 hours.

## Similar
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89433
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [AIHawk](https://affpapa.org/en/nevibecode/mcp/aihawk.md) — MCP server · ★ 32221
- [Skyvern](https://affpapa.org/en/nevibecode/mcp/skyvern.md) — MCP server · ★ 23263
- [SeleniumBase MCP](https://affpapa.org/en/nevibecode/mcp/seleniumbase-mcp.md) — MCP server · ★ 13169
- [Inbox Zero](https://affpapa.org/en/nevibecode/mcp/inbox-zero.md) — MCP server · ★ 12791

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md