tolpo runs on your own machine — the client starts it, so there is no endpoint to ping. 308 installs a week from npm. Last commit 14 Oct 2026.
Local-first control of TP-Link Tapo smart-home devices for AI agents
Today is the operative word: we check tolpo every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tolpo -- npx -y tolpo
{
"mcpServers": {
"tolpo": {
"args": [
"-y",
"tolpo"
],
"command": "npx"
}
}
}
[mcp_servers.tolpo]
command = "npx"
args = ["-y", "tolpo"]
{
"mcpServers": {
"tolpo": {
"args": [
"-y",
"tolpo"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"tolpo": {
"args": [
"-y",
"tolpo"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
TAPO_EMAIL (Email of the Tapo account the devices belong to), TAPO_PASSWORD (Password of that Tapo account).
The author declared them in the registry entry; get the values from the project itself.
MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents
MCP server for Tasmota devices: status, power control. Local-first smart home.
Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation.
MCP server for Hubitat: devices, status, commands via Maker API. Local-first smart home.
Local-first AI CLI usage analytics for agents.
Local-first PDF tools for AI agents: merge, split, extract, render, compress. Files stay on-device.
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
Answers built from our own checks of this server.