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?
Provides local, offline validation of MQTT topic strings against the Sparkplug B topic grammar and checks Unified Namespace topic paths for naming consistency issues such as inconsistent depth, mixed casing, duplicates, empty levels, and stray wildcards. It does not connect to an MQTT broker.
Why this server?
Allows the architecture agent to propose adding an MQTT connector to a record, so an AimDB topology can be wired up to MQTT topics as part of a proposed (and later confirmed) architecture change.
Why this server?
Allows monitoring MQTT broker connectivity as a check type.
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?
Allows subscribing to MQTT topics, reading buffered messages, unsubscribing, and listing active subscriptions via an MQTT broker.
Why this server?
Allows publishing messages to an MQTT broker via the publish_message tool, enabling agents to send notifications or data to MQTT topics.
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?
Provides an adapter for reading timestamped events from MQTT topics, allowing agents to correlate physical camera frames and timeline data with MQTT event streams.
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
