# Tapo MCP [Health: Active]

**Category:** 🏠 Home Automation  
**Repository:** https://github.com/mihai-dinculescu/tapo  
**GitHub Stars:** 862  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tapo-mcp

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "tapo-mcp": {
    "command": "uvx",
    "args": ["tapo"],
    "env": {
      "TAPO_USERNAME": "",
      "TAPO_PASSWORD": "",
      "IP_ADDRESS": ""
    }
  }
}
```

**Requires environment variables:** `TAPO_USERNAME`, `TAPO_PASSWORD`, `IP_ADDRESS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Tapo MCP MCP server does

The Tapo MCP MCP server connects AI agents to TP-Link Tapo smart home devices through the Model Context Protocol. It exposes Tapo devices as AI-callable tools and resources, allowing an MCP client to discover available hardware and issue supported control operations.

The project’s supported-device list covers multiple Tapo product families. Tested examples include L510, L520, L530, L535, L610, and L630 bulbs; L900, L920, and L930 light strips; P100, P105, P110, P110M, and P115 plugs; and P300, P304M, P306, P316M, and related power strips. It also lists hubs, switches, sensors, and cameras, including models such as H100, S200B, T100, and C210. The complete feature matrix is maintained in the repository’s supported-devices documentation.

## How it works

The Tapo MCP MCP server uses the repository’s unofficial Tapo API client to communicate with TP-Link Tapo hardware. The MCP layer presents those devices to an AI agent as tools and resources rather than requiring the agent to call the Tapo API directly.

The underlying project includes Rust and Python client libraries. Both library examples authenticate with a Tapo username and password, then address a device using its local IP address. The MCP server has its own README for setup and usage, but the supplied project excerpt does not describe its transport, command names, or complete configuration flow.

## Setup and configuration

Use the setup instructions in the `tapo-mcp` directory of the repository for MCP-specific installation and client configuration.

For the underlying Tapo libraries, the documented credential variables are `TAPO_USERNAME` and `TAPO_PASSWORD`. The examples also use `IP_ADDRESS` for a target device.

## Tools and capabilities

The Tapo MCP MCP server is intended for agents that need to:

- Discover TP-Link Tapo devices.
- Control compatible Tapo hardware through AI-callable MCP tools.
- Access exposed device resources through MCP.
- Work with supported bulbs, light strips, plugs, power strips, hubs, switches, sensors, and cameras.

The exact tool names, arguments, return values, and per-model operations are not provided here. Consult the repository’s MCP documentation and supported-device matrix before building an agent workflow around a particular device feature.

## Limitations and notes

This is an unofficial Tapo API client and MCP server. Device support varies by model, and the README points to a separate feature matrix for the authoritative list.

It also does not document remote access, cloud deployment, authentication beyond the Tapo account credentials shown for the libraries, or a specific MCP transport. Treat those areas as configuration questions to verify in the `tapo-mcp` README.

_Full upstream README: https://allmcps.com/mcp/tapo-mcp/readme_