Manage MQTT brokers from your AI assistant
Updated October 15, 2026
claude mcp add mqtizer --env MQTIZER_TOKEN=mqz_pat_... -- npx -y @mqtizer/mcpAfter installing, replace mqz_pat_... with the token you create in the app (Settings, MCP access).
The Mqtizer MCP server connects an AI client to your Mqtizer account. Ask it in plain language to add a broker, invite a teammate, edit a template, or connect to a broker and watch what arrives. Every change shows up in the app, because the server works through the same Mqtizer API the app uses.
It runs on your own machine, signs in with a token you create in the app, and is published on npm as @mqtizer/mcp.
What you need
- Node.js 20 or later.
- A Mqtizer account. Guest mode has no account, so it cannot create a token.
- An MCP client: Claude Code, Claude Desktop, Cursor, or another client that runs local (stdio) MCP servers.
1. Create a token in the app
Open Settings, MCP access in the Mqtizer app and create a token. Copy it right away: it is shown once.
- Read lets the assistant look at your workspaces, brokers and templates, and connect to your brokers.
- Write also lets it change them. Your workspace role still limits what it can change.
Tokens expire after 30, 90 or 365 days. You can revoke one in the same screen at any time, and the app shows when each token was last used.
2. Add the server to your client
Claude Code
claude mcp add mqtizer --env MQTIZER_TOKEN=mqz_pat_... -- npx -y @mqtizer/mcp
Claude Desktop, Cursor and most other clients. Add this to the client's MCP configuration (claude_desktop_config.json for Claude Desktop, ~/.cursor/mcp.json for Cursor). The app shows the same snippet, with your token filled in, right after you create one.
{
"mcpServers": {
"mqtizer": {
"command": "npx",
"args": ["-y", "@mqtizer/mcp"],
"env": { "MQTIZER_TOKEN": "mqz_pat_..." }
}
}
}
3. Ask for something
Restart the client, then try:
- "List my Mqtizer brokers."
- "Add a broker for broker.example.com on port 8883 with TLS to the Site B workspace."
- "Connect to the staging broker, subscribe to sensors/#, and tell me what arrives in the next minute."
- "Create a template called heartbeat that publishes the battery level."
What it can do
| Area | Tools |
|---|---|
| Workspaces and members | list, create, update, delete; invite, accept, remove, change roles |
| Brokers | list, get, create, update, move, delete |
| Templates | list, create, update, delete |
| Live connections | connect, subscribe, unsubscribe, publish, read messages, disconnect |
Live connections run from your machine with TCP, TLS, WebSocket or secure WebSocket, following each broker's settings. A token cannot create other tokens, edit your profile or delete your account.
Your passwords stay out of the chat
Broker passwords, client keys and certificates never reach the AI model. Tool results show them as [redacted]. When the assistant connects to a broker, the server loads the credentials itself and hands them to the MQTT connection, and it removes them from any error message.
To keep a stored password while editing a broker, leave the field out (or send [redacted]). Send a new value to replace it.
If something goes wrong
- "The API does not accept this token." The token expired or was revoked. Create a new one in the app and update
MQTIZER_TOKEN. - "Not allowed." The token is read-only, or your workspace role does not permit the change.
- "Rate limit reached." A token can make 120 requests a minute. Wait a minute and try again.
Questions or problems: write to support@mqtizer.com.