Mqtizer
NewMCP server for Claude and Cursor

The AI-native MQTT clientfor professional teams.

Tell your AI assistant which broker you need. It sets it up and writes the payload templates, and your whole team has both on iPhone, iPad, Android and Mac.

  • Coming soonApp Store
  • Coming soonGoogle Play
  • Coming soonMac App Store
Mqtizer MQTT client on Mac showing brokers and workspaces
Mqtizer MQTT client on iPhone showing the same dashboard

Sharing a broker still means pasting its password into a chat.

Mac · New broker
Hostbroker.site-a.example
Port8883
Usernamesite-a
Password••••••••
Connected
Lena
Gateway login for Site A:broker.site-a.example
8883
site-a / S1te-A!2026
Thanks, typing it in now
New broker
Hostbroker.site-a.example
Port8833
Usernamesite-a
Connection failedBroker unreachable. Check the host, port and TLS settings.
Mira
••••••••
Authentication failed
Jonas
••••••••
Authentication failed
Lena
••••••••
Authentication failed
Ben
••••••••
Authentication failed
Aiko
••••••••
Authentication failed
Sam
••••••••
Authentication failed
Or skip all of it. Let your assistant do the first one.See how
Mac · New broker
Hostbroker.site-a.example
Port8883
Usernamesite-a
Password••••••••
Connected
1times this broker has been typed in by hand

Ask for a broker. Get one your whole team can use.

Connect Claude, Cursor or any MCP client to your workspaces. It adds brokers, edits templates and tests connections from your machine.

  • A token you control

    Create it in the app, choose read or write, and revoke it whenever you like. It expires on its own.

  • Passwords stay out of the chat

    The model only ever sees [redacted]. Credentials are used inside the server on your machine.

  • The same rules as the app

    Workspace roles and plan limits apply to every change it makes.

Set up the MCP server

Add our Site A gateway and a GPS heartbeat template, then check it connects.

Gateway is in Site A and connects over TLS. gps_heartbeat fills in live GPS from each phone. I only see the password as [redacted].

Your team opens the app. It's already there.

Whatever your assistant, or you, sets up lands in the workspace: hosts, certificates, last will, topics. Teammates just tap Connect.

Mac · Site A · Gateway
NameGateway
Hostbroker.site-a.example
Port8883
TypeTCPWebSocket
WebSocket path/mqtt
A teammate's phone
Site A
Gateway
TLSMQTT 5.03 topicslast will
broker.site-a.example:8883
Sensorssensors.site-a.example:8883
Connect
A workspace per site
Group brokers by site, client or project.
Roles, not shared passwords
Invite teammates by email, then set them as admin, editor or peer.

Then it goes to work in the field.

AllQoS 1Retained
sensors/kitchen/temp · QoS 1
{"c": 21.4}
cmd/lamp/set · QoS 0
on
status/gateway · QoS 1 · retained
online
sensors/door/open · QoS 2
{"open": true}
cmd/fan/speed · QoS 1
3
ACCEL · m/s²0.12 · 9.81 · 0.04
GYRO · rad/s0.01 · -0.02 · 0.00
GPS52.5200, 13.4050±4 m
BATTERY82%
payload
{"gps": [52.52, 13.405], "battery": 82}
template
{"lat": {{GPS_LAT}},
 "batt": {{BATTERY_LVL}}}
sent
{"lat": 52.52, "batt": 82}
privateworkspacepublic
148/ 200
42 msg/s
CountDurationStop burst
broker / messageslive
AllQoS 1Retained
sensors/kitchen/temp · QoS 1
{"c": 21.4}
cmd/lamp/set · QoS 0
on
status/gateway · QoS 1 · retained
online
sensors/door/open · QoS 2
{"open": true}
cmd/fan/speed · QoS 1
3

Enterprise-grade security, from phone to server.

Passwords, keys and certificates are encrypted on your phone and on our servers, and only travel over HTTPS. Your MQTT messages never reach us at all: the app talks straight to your broker.

  1. On your phone

    Encrypted on the device.

  2. On the way

    HTTPS to us, TLS to your brokers.

  3. On our servers

    Encrypted before it is saved.

Works at your desk and out on site.

MQTT 3.1.1 and 5.0

Over TCP, WebSocket or TLS. It gets through HTTP proxies and talks to secured brokers.

Offline first

Your message log is saved on your device, never on our servers. It survives lost connections and app restarts.

Every device you carry

iPhone, iPad, Android and Mac, with the same workspace on each.

Keeps listening

On Android, your brokers stay connected while the app is in the background.

Take the log with you

Export messages as text, JSON or CSV for a ticket, a teammate or a spreadsheet.

Free to start. Pro is on the way.

Every feature is in every plan, MCP access included. The plans differ only in how much fits in them.

Free

€0

For you and a small team, on every device.

team members
3
brokers per workspace
3
workspace
1
templates
10

Pro

Coming soon

For teams with more sites, brokers and people.

team members
10
brokers per workspace
25
workspaces
5
templates
100

Need room for a larger team now? Write to support@mqtizer.com

Questions people ask first.

Any broker that speaks MQTT 3.1.1 or 5.0 over TCP or WebSocket, with or without TLS. You can add your own CA, client certificates and a PKCS#12 bundle.

Yes. Mqtizer runs on iPhone, iPad, Android and Mac, and your workspace is the same on every one of them.

Yes, to start. The free plan covers 3 team members, 3 brokers and 10 templates in one workspace, with every feature included. A Pro plan with higher limits is coming soon.

Invite them by email and give each person a role: admin, editor or peer. They open the app and the workspace is already there.

Yes. Broker passwords, keys and certificates are encrypted on your phone and on our servers. The app talks to its backend over HTTPS, and brokers can use TLS with your own certificates.

Your message log is still there, even after you restart the app.

Yes. The Mqtizer MCP server connects Claude, Cursor and other AI clients to your workspaces with a token you create in the app. It can add brokers, edit templates and test connections, and broker passwords never reach the model.

No. As a guest you get one workspace with two brokers on one device. Sign in to share workspaces with your team and use them on your other devices.

Yes. Subscribe to topics with + and # wildcards, publish with QoS 0, 1 or 2, simulate a device with live sensor data from your phone, and fire a burst by count or duration to load-test the broker.

No. The app connects straight from your device to your broker, and the message log is saved only on that device. Our servers keep your workspaces, broker settings and templates, never your messages. Messages you read through the MCP server go to the AI assistant you connected.

Your next broker takes ten minutes. Your team's takes none.

Free to start on iPhone, iPad, Android and Mac.

  • Coming soonApp Store
  • Coming soonGoogle Play
  • Coming soonMac App Store