From mqtt
Set up the MQTT channel — save the broker URL, credentials, and review connection status. Use when the user provides an MQTT broker URL, asks to configure MQTT, asks "how do I set this up", or wants to check channel status.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mqtt:configureThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes connection settings to `~/.claude/channels/mqtt/.env` and orients the
Writes connection settings to ~/.claude/channels/mqtt/.env and orients the
user on subscription and access policy. The server reads .env at boot.
Arguments passed: $ARGUMENTS
Read the state files and give the user a complete picture:
Broker URL — check ~/.claude/channels/mqtt/.env for
MQTT_BROKER_URL. Show set/not-set; if set, show the URL with password
masked if embedded in the URL.
Auth — check for MQTT_USERNAME in .env. Show set/not-set.
Never display the password.
Client ID — check for MQTT_CLIENT_ID in .env. Show if set,
otherwise mention the default prefix claude-mqtt.
Subscriptions — read ~/.claude/channels/mqtt/config.json if it
exists. Show subscription count and list topics. Show allowlist state.
What next — end with a concrete next step based on state:
/mqtt:configure <broker-url> with your MQTT
broker URL (e.g., mqtt://localhost:1883)."/mqtt:access subscribe add <topic>."claude --channels plugin:mqtt@apoco-plugins to start
receiving messages."<broker-url> — save itDetect this case when $ARGUMENTS starts with mqtt:// or mqtts://.
$ARGUMENTS as the broker URL (trim whitespace). Validate it
starts with mqtt:// or mqtts://.mkdir -p ~/.claude/channels/mqtt.env if present; update/add the MQTT_BROKER_URL= line,
preserve other keys. Write back, no quotes around the value.chmod 600 ~/.claude/channels/mqtt/.env — the URL may contain credentials.auth <username> <password> — save credentials$ARGUMENTS (after "auth").mkdir -p ~/.claude/channels/mqtt.env if present; update/add MQTT_USERNAME= and
MQTT_PASSWORD= lines, preserve other keys. Write back.chmod 600 ~/.claude/channels/mqtt/.envclient-id <prefix> — set client ID prefix$ARGUMENTS (after "client-id").mkdir -p ~/.claude/channels/mqtt.env; update/add MQTT_CLIENT_ID= line. Write back.chmod 600 ~/.claude/channels/mqtt/.envclear — remove credentialsDelete MQTT_BROKER_URL=, MQTT_USERNAME=, MQTT_PASSWORD=, and
MQTT_CLIENT_ID= lines from .env (or the file if those are the only lines).
.env once at boot. Changes need a session restart
or /reload-plugins. Say so after saving.config.json is re-read on every tool call — subscription/allowlist changes
via /mqtt:access take effect immediately, no restart.npx claudepluginhub apocohq/claude-plugins --plugin mqttGuides securing MQTT broker and client deployments with authentication, topic ACLs, TLS, and payload encryption. Use when building, reviewing, or auditing MQTT or IoT messaging security.
Guides MQTT messaging patterns for IoT systems: topic hierarchy design, QoS selection, retained messages, LWT for presence, broker deployment, and MQTT 5.0 features like shared subscriptions.
Set up the Matrix channel — save credentials, check status, and review configuration. Use when the user pastes Matrix credentials, asks to configure Matrix, asks "how do I set this up," or wants to check channel status.