You have an ESP32 on the bench, a Home Assistant box in the cupboard and a Node-RED flow half-wired — and every one of them is waiting on a broker you have not stood up yet. Spinning up Mosquitto on a laptop or renting a cloud broker just to watch two sensors talk is more friction than the job deserves. MQTT Server & Broker Pro removes that step: the phone in your pocket becomes the broker.
It is a genuine broker, not a client pointed at someone else's server. Start it, and your devices connect straight to the phone over Wi-Fi, a hotspot or cellular — it binds to every local IPv4 interface — so an MQTT network comes up in seconds with nothing else running.
The broker opens the endpoints real deployments need. Plain MQTT over TCP on port 1883 is on by default; a WebSocket listener on 8083 (path /mqtt) lets browser dashboards connect; and the secure pair — TLS on 8883 and WSS on 8084 — carries encrypted traffic with your own certificate and key. Every port is editable, and the listeners screen shows each endpoint as a QR code so a device or teammate can scan the address instead of typing it.


Debugging is about visibility, so the broker keeps a live console of up to 3,000 events, newest first, that you can pause, resume and narrow with a topic filter. The Clients tab lists who is connected with online and idle filters, and tapping a client opens the full picture — subscriptions, last will, keep-alive and next ping, published and received counts, and address — with one tap to disconnect or ban an IP.
You do not need a second app to check the wiring. The Client tab is a real MQTT client built in: publish to any topic at QoS 0, 1 or 2 with an optional retain flag, subscribe to a filter, and watch the acknowledgements (PUBACK, PUBCOMP) come back. Republish any message you captured in the log straight from its detail view.
For anything beyond a bench test, turn on authentication. Create users with roles — admin, device or read-only — where passwords are stored as salted, stretched SHA-256 hashes, never in the clear. Then write access rules that allow or deny publish, subscribe or both on a topic filter, evaluated in order, so a sensor can only post to its own branch while a dashboard reads everything.
tcp://192.168.1.20:1883.test/#.The broker, the live log, the test client, the topic tree and the first hour of stats are free, with ads, and allow up to 10 connected clients. Pro removes the ads and unlocks WebSockets, Auth & ACL, SQLite history, TLS and long-range stats, as a monthly or yearly subscription or a one-time lifetime purchase, with a 24-hour trial.
This is a local-network broker: devices reach it on the phone's IP, so keep the phone on the same network while it serves. TLS listeners need a certificate and key you supply. The free tier shows ads and caps simultaneous clients at 10; everything runs on the device with no account.
It is a real broker — your devices connect directly to the phone. A separate test client is built in so you can publish and subscribe to check it.
MQTT over TCP (1883), WebSocket (8083, path /mqtt), and the secure TLS (8883) and WSS (8084) listeners, all with editable ports.
Yes. Pro adds users with admin, device or read-only roles and per-topic access rules for publish and subscribe; passwords are stored as salted SHA-256 hashes.
With Pro, messages persist to an on-device SQLite database you can browse and export to CSV or JSON. The free tier keeps a live log of up to 3,000 events.