A diagnostic-oriented MQTT client tool supporting MQTT 5.0/3.1.X, multiple brokers, operations logs, and topic filtering.
MQTT Board is a diagnostic-oriented MQTT client tool built for developers working with MQTT brokers. It supports MQTT 5.0 and 3.1.X protocols, allows connections to multiple brokers, and provides detailed operations logs with advanced topic filtering. The tool runs entirely in the browser and saves configurations locally, making it ideal for quick testing and debugging of MQTT-based systems.
IoT developers, embedded systems engineers, and backend developers who need to test, debug, or monitor MQTT-based messaging systems in real-time.
Developers choose MQTT Board for its diagnostic-focused features, support for multiple brokers and protocol versions, and flexible integration options as a standalone app, Vue component, or iframe embed—all without requiring server-side deployment.
Diagnostic-oriented MQTT client tool. Supports MQTT 5.0 and 3.1.X protocols, connections to multiple brokers, MQTT operations logs and multiple subscribe widgets with unique/history topic filtering mode. Saves configuration in browser's local cache.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports simultaneous connections to multiple MQTT brokers, enabling cross-broker debugging and monitoring in a single interface, as highlighted in the features list.
Fully compatible with both MQTT 5.0 and 3.1.X protocols, allowing developers to test advanced features like properties and user-defined options, as shown in the settings structure.
Provides detailed logs of all MQTT operations, essential for real-time debugging and analysis of message flows, which is core to its diagnostic focus.
Can be used standalone, embedded as a Vue component, or via iframe, offering versatility for different deployment scenarios, as documented in the README.
Integration as a component requires a Quasar-based Vue app, limiting its use in projects with other frameworks and adding complexity for non-Vue developers.
Setting up locally involves Node.js, npm, and Quasar installation, which is heavier and more involved compared to pre-built, zero-configuration tools.
Saves configurations only in browser local cache, lacking server-side storage, cloud sync, or collaborative features, which restricts use in team environments.