Legacy MQTT.fx downloads and MQTT testing guides
Understand MQTT client basics before choosing a tool.
An MQTT client can be a device, service, command-line script, mobile app, or desktop tool. It connects to an MQTT broker, publishes messages to topics, subscribes to topic filters, or does both.
Desktop clients are useful because they remove application code from the first debugging step. If the desktop client cannot connect, the problem is usually credentials, host, port, TLS, network access, or broker policy.
Create a broker connection, subscribe to `test/#`, publish a message to `test/hello`, and confirm the payload appears in the subscribed message list.
After the basic flow works, add TLS, username/password, retained messages, QoS, and MQTT 5 properties one at a time.
Enter the broker host, port, client ID, credentials, and TLS settings, then connect and subscribe to a known test topic.
They are used by IoT devices, backend services, desktop debugging tools, and scripts to exchange messages through an MQTT broker.