Tasmota MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 61 installs a week from npm.
MCP server for Tasmota devices: status, power control. Local-first smart home.
The linked repository no longer exists on GitHub — it was deleted or made private.
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
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 tasmota-mcp -- npx -y tasmota-mcp
{
"mcpServers": {
"tasmota-mcp": {
"command": "npx",
"args": [
"-y",
"tasmota-mcp"
]
}
}
}
[mcp_servers.tasmota-mcp]
command = "npx"
args = ["-y", "tasmota-mcp"]
{
"mcpServers": {
"tasmota-mcp": {
"command": "npx",
"args": [
"-y",
"tasmota-mcp"
]
}
}
}
{
"servers": {
"tasmota-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tasmota-mcp"
]
}
}
}
MCP server for Hubitat: devices, status, commands via Maker API. Local-first smart home.
Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation.
Local-first control of TP-Link Tapo smart-home devices for AI agents
MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents
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
MCP server for Philips Hue smart lighting control
LAN-first, cloud-fallback MCP server for Govee smart lights and devices.
Answers built from our own checks of this server.