IoT Device Management MCP Server
Related Servers
Alternatives to IoT Device Management MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.535 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and humans to control various hardware boards (ESP32, Arduino, Raspberry Pi, etc.) through a unified API via MCP, with real-time dashboard support.MIT
- FlicenseBqualityDmaintenanceControl real robots and IoT devices through AI agents. Self-register with wallet authentication, pay with ETH for tier upgrades, and execute Vision-Language-Action commands. Features robot control, sensor monitoring, multi-agent coordination, and autonomous payments.81-

AIoT MCP Serverofficial
FlicenseAqualityDmaintenanceA Model Context Protocol server for AI agents to discover and control IoT devices through MQTT, using the AIoT Agent Network Protocol for device registration and communication.31-- AlicenseNot gradedqualityBmaintenanceA local capability layer for AI agents providing persistent memory, credential management, connectors, and activity tracking.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control and monitor Home Assistant smart home devices through natural language interactions. Supports device control, entity state monitoring, history access, and automation generation with both MCP protocol and standalone HTTP REST API modes.1MIT
TDQS
Scored across 9 tools
Most tools have clear distinct purposes, though device_analytics and get_fleet_dashboard both provide overviews and could cause slight confusion. However, descriptions help differentiate them.
All tool names follow a consistent snake_case verb_noun pattern (e.g., register_device, get_alerts, send_command) with no mixing of conventions.
9 tools cover the essential IoT device management operations well, including registration, listing, status, alerts, commands, and firmware updates. Not too few or too many.
Missing crucial device lifecycle operations: no update_device to modify attributes (e.g., location, name) and no delete_device to remove devices. These gaps can cause agent failures when managing device lifecycles.