Secure · Private · On your device

Secure by design.
Private by default.

No cloud, no account, no telemetry. Every broker, client, credential and certificate stays encrypted on your device — MQTT Connect is built so there's nothing to leak, because there's nowhere for it to go.

Live on the App Store and Google Play · fully private

0trackers or analytics SDKs
256-bitencryption at rest
0data ever leaves your device
Connections
⚙︎
2 live · 7 subscriptions · 3 clients
Factory Floor — Line 3
live
128
tls://broker.line3.internal:8883  ▣ cert
4 subs128 msgs2h 14m Disconnect
Home Assistant
live
36
wss://home.example.net:443
3 subs36 msgs41m Disconnect
Staging
fault
tls://staging.mqtt.io:8883
2 savedlast ok 3d ago Retry
connect ECONNREFUSED · check firewall / port 8883
Add client
Features

Built for people who actually run brokers.

Every screen is designed around the workflow of debugging and operating real MQTT deployments — not a toy demo client.

▣

Client certificates & mTLS

Import CA certs, client certs and keys from PEM, paste them directly, or unlock a .p12 bundle in one step — full mutual TLS, no laptop required.

≋

Live message feed

Watch subscribed topics stream in real time, expand any message for QoS, retain flag and payload, and re-send or edit-and-send instantly.

▤

Publish composer

Compose JSON, text, or Base64 payloads with topic autocomplete drawn from your history, and pin frequent sends as snippets.

⌁

TCP, TLS, WS & WSS

Full MQTT 3.1.1 and 5.0 support over every standard transport, with per-client keep-alive, clean-session, and timeout controls.

⏣

Smart topic suggestions

Subscriptions and publishes both surface topics you've used before on that client, so you're never retyping long topic paths.

◆

Brokers & clients, kept apart

Save a broker's host, port and transport once, then create as many clients against it as you need — each with its own ID, auth and certs.

⇄

Encrypted backup & restore

Export any set of clients and brokers — credentials and certificates included — into a single AES-256 file locked with a password only you know, and import it back on another device.

Security & privacy

Your credentials never leave your device.

There's no account, no backend, and nothing phoning home — private by default. MQTT Connect only talks to the brokers your clients connect to.

✓
Encrypted at rest

Broker profiles, clients, usernames, passwords and certificates are held in the OS keychain and encrypted storage — never in plain text.

✓
Offline, no telemetry

No analytics SDKs, no crash reporters phoning a server, no usage tracking of any kind.

✓
Face ID & auto-lock

Gate the app behind biometrics, auto-lock after inactivity, and hide payload previews in the app switcher.

✓
Certificates stay put

Client certificates and private keys are read once through the system file picker and stay on-device unless you explicitly export them.

✓
Password-encrypted backups

Exports are locked with AES-256 and a password only you choose — the file is useless to anyone without it, on or off your device.

$ mqtt-connect · settings · security
› Require Face ID to open   ON
› Lock after   5 minutes
› Hide payloads in app switcher   ON
 
$ mqtt-connect · settings · data
› Export clients & brokers   encrypted
› Import clients & brokers
› Erase all data   local only
 
MQTT Connect 1.2 — offline · no telemetry
Inside the app

A workspace for every connection.

Tabs for topics, publishing, and the live feed — all scoped to the client you're working in.

Client certificate

mTLS · factory-floor-line-3
CA certificateca.pem ✓
Client certificateclient.crt ✓
Client private keyclient.key ✓
import .p12paste PEM

Live feed

factory-floor-line-3
14:02:11RXline3/sensors/temp
14:02:14TXline3/cmd/reset
14:02:19RXline3/sensors/humidity
14:02:24RXline3/status/heartbeat
Q1retained42 B

Publish

line3/cmd/reset
JSONTextBase64
{ "reset": true, "delay_ms": 500 }
QoS 1retain offpin to feed

Topics

4 active · 9 saved
●line3/sensors/#Q1
●line3/status/heartbeatQ0
○line3/alerts/+Q2
line3/sensors/templine3/cmd/reset
Shreyansh Jain
Why I built this

I'm the CTO of an IoT company, managing all kinds of connected devices day to day — and MQTT Connect exists because I needed it myself. Built with care, it's exactly the MQTT client I wanted on my own phone.

I've also built SSH Connect, an offline SSH client and encrypted vault, plus a few other privacy-first apps — see everything I've made.

Take your clients with you.

MQTT Connect is live on the App Store and Google Play.

App Store
Available now

MQTT Connect is live on the App Store — download it now.

Download on the App Store
Google Play
Available now

MQTT Connect is live on Google Play — download it now.

Get it on Google Play

Privacy policy · Terms of use