MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
{
"TAPO_MCP_USERNAME": "YOUR_SECRET_VALUE",
"TAPO_MCP_PASSWORD": "YOUR_SECRET_VALUE",
"TAPO_MCP_DISCOVERY_TARGET": "YOUR_VALUE_HERE",
"TAPO_MCP_API_KEY": "YOUR_SECRET_VALUE",
"TAPO_MCP_DISCOVERY_TIMEOUT": "5",
"OTEL_EXPORTER_OTLP_ENDPOINT": "YOUR_VALUE_HERE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-mihai-dinculescu-tapo-mcp": {
"url": "https://io-github-mihai-dinculescu-tapo-mcp.example.com"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Tapo MCP is an MCP server for MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents. It supports HTTP transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
Tapo MCP uses HTTP transport. Use the package or command config in Install.
Tapo MCP inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Tapo MCP is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/mihai-dinculescu/tapo-mcp:0.3.1streamable-http | oci | Not captured | Env: TAPO_MCP_USERNAME required secret Env: TAPO_MCP_PASSWORD required secret Env: TAPO_MCP_DISCOVERY_TARGET required Env: TAPO_MCP_API_KEY secret Env: TAPO_MCP_DISCOVERY_TIMEOUT Env: OTEL_EXPORTER_OTLP_ENDPOINT |