Log inSubmit server
Tapo MCP logo

Tapo MCP

Discovers and controls supported TP-Link Tapo smart home devices through AI-callable MCP tools and resources.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Tapo MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tapo-mcp": {
      "command": "uvx",
      "args": [
        "tapo"
      ],
      "env": {
        "TAPO_USERNAME": "YOUR_VALUE_HERE",
        "TAPO_PASSWORD": "YOUR_VALUE_HERE",
        "IP_ADDRESS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx tapo

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 25d ago.

Overview

Tapo MCP MCP server exposes TP-Link Tapo devices to AI agents through the Model Context Protocol. It supports device discovery and control for compatible bulbs, strips, plugs, power strips, hubs, switches, sensors, and cameras. The server is a fit for agents that need to inspect or operate Tapo hardware on a home network. The repository also provides Rust and Python Tapo client libraries, while MCP setup details are maintained separately.

Use cases

  • Discover Tapo devices available to an AI agent
  • Control compatible Tapo lights and plugs
  • Operate supported Tapo sensors, switches, hubs, or cameras
  • Build home automation workflows around local Tapo hardware

Key features

  • Exposes Tapo devices as MCP tools and resources
  • Discovers supported TP-Link Tapo hardware
  • Controls compatible bulbs and light strips
  • Supports plugs and power strips
  • Covers selected hubs, switches, sensors, and cameras

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 15d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · tapo (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars862Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Tapo MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Tapo MCP

Tapo MCP is an MCP server that connects AI agents to TP-Link Tapo smart home devices. Its main tools and resources support discovering and controlling compatible bulbs, light strips, plugs, power strips, hubs, switches, sensors, and cameras through the Model Context Protocol.

Use the setup instructions in the repository’s `tapo-mcp` directory.

The documented Tapo library examples use `TAPO_USERNAME` and `TAPO_PASSWORD` for account credentials, plus `IP_ADDRESS` when targeting a device.

Tapo MCP supports the device models listed in the repository’s supported-device matrix, including selected bulbs, light strips, plugs, power strips, hubs, switches, sensors, and cameras.

The README identifies the MCP interface and links to separate setup documentation, but it does not name Cursor or any other MCP client.

Related MCP servers

All in Home Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTapo MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tapo-mcp?style=directory)](https://allmcps.com/mcp/tapo-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tapo-mcp"><img src="https://allmcps.com/api/badge/tapo-mcp?style=directory" alt="Tapo MCP on AllMCPs" /></a>