NewMCP server for Claude and Cursor

The AI-native MQTT clientfor your whole team.

Ask Claude, Cursor or any AI assistant to set up your MQTT broker through MCP. Then publish, subscribe and test your IoT devices on iPhone, iPad, Android and Mac, with your whole team in one shared workspace.

Mqtizer MQTT client on Mac showing brokers and workspaces
Mqtizer MQTT client on iPhone showing the same dashboard

One app, every device

The whole app, on every device your team uses.

Connect to any MQTT broker, publish and subscribe live, reuse payload templates, invite your team and hand it all to your AI assistant over MCP.

How teams share brokers today

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

  • The password stays in the chat history for good.
  • One wrong digit and nothing connects. The error doesn't say why.
  • Change the password, and everyone types it in again.
There is an easier way.See how
There is an easier way.See how

AI-native, through MCP

Ask your AI for an MQTT broker. Your whole team gets it.

Mqtizer has its own MCP server, so Claude, Cursor or any MCP client can work with your MQTT setup. MCP is the open standard AI assistants use to talk to apps. Your assistant adds brokers, writes payload templates, subscribes to topics and tests connections, right from your computer.

  • 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].

What your team sees

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

Every broker is saved in a shared workspace, with its host, certificates and topics. Your teammates open the app and tap 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 member.
Change it once
Edit a broker once. Teammates get the change the next time their app syncs.

Testing and debugging

Publish and subscribe to MQTT topics from anywhere.

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

How your data stays safe

Your passwords stay encrypted, from phone to server.

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

On your phone

Encrypted on the device.

↓ HTTPS
Passwords, keys, certificates

On our servers

Encrypted before it is saved.

↓ MQTT
MQTT messages

Your broker

Your MQTT messages go straight here, over TLS when your broker offers it. They never reach us.

Built for daily work

An MQTT client built for IoT work, at the desk and on site.

MQTT 3.1.1 and 5.0

Over TCP or WebSocket, with or without TLS, including your own CA and client certificates.

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.

What it costs

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
workspaces
2
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

Good to know

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 2 workspaces with 3 team members and 3 brokers each, and 10 templates, 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 member. 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.

Let your AI assistant add your first broker.

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