Tasmota MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 23 Sep 2026.
MCP server for Tasmota devices: status, power control. Local-first smart home.
Today is the operative word: we check Tasmota MCP 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 tasmota-mcp -- npx -y tasmota-mcp
{
"mcpServers": {
"tasmota-mcp": {
"args": [
"-y",
"tasmota-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.tasmota-mcp]
command = "npx"
args = ["-y", "tasmota-mcp"]
{
"mcpServers": {
"tasmota-mcp": {
"args": [
"-y",
"tasmota-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"tasmota-mcp": {
"args": [
"-y",
"tasmota-mcp"
],
"command": "npx"
}
}
}
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.
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.
MCP server for LIFX lights: list, state, power control. Needs a free API token.
Answers built from our own checks of this server.