MQTT is a lightweight messaging protocol for IoT devices that enables efficient communication in low-bandwidth, high-latency, or unreliable networks. It uses a publish/subscribe model and is designed for constrained devices and networks.
Why this server?
Core integration allowing communication with IoT devices using MQTT protocol for publishing/subscribing to commands and responses
Why this server?
Bridges AI models with the physical world using the MQTT protocol, enabling the publishing of control commands and subscription to device status updates for IoT hardware.
Why this server?
Provides tools for publishing messages to MQTT topics and subscribing to MQTT topics to receive messages, with configurable broker connection settings including authentication and TLS support.
Why this server?
Employs the MQTT protocol for real-time printer communication, allowing for job management and G-code command dispatch.
Why this server?
Provides capabilities to ingest event data via MQTT and forward data streams to MQTT brokers for real-time messaging and IoT integration.
Why this server?
Provides tools for interacting with MQTT brokers, enabling AI agents to subscribe to topics, store messages with timestamps, query historical data, detect silent topics, monitor connection gaps, and optionally publish messages.
Why this server?
Interacts with MQTT brokers and Sparkplug B payloads. Supports reading topic values, bounded subscriptions, node discovery, and UNS (Unified Namespace) browsing. Publish operations are high-risk and require MOC approval.
Why this server?
Supports monitoring and debugging of the MQTT integration within Home Assistant, enabling searches for related entities and access to integration-specific debug logs.
Why this server?
Allows interaction with MQTT clusters on EMQX Cloud or self-hosted clusters, enabling clients to list connected MQTT clients, retrieve client information, disconnect clients, and publish messages to MQTT topics