MQTT Observability
April 18, 2026 · View on GitHub
Observe and interact with an MQTT broker from inside Claude Code — monitor all traffic, watch a specific topic, or publish a payload. Credentials are collected once and reused across invocations.
What's inside
Command
/mqtt-setup— first-run setup. Collects broker host/IP, port, broker type, username, password, TLS flag, and persists them to~/.claude/plugins-data/mqtt-observability/credentials.env. Re-run any time to rotate credentials.
Skills
mqtt-monitor-all— subscribe to#and stream every payload on the broker.mqtt-monitor-topic— subscribe to a specific topic or wildcard pattern (e.g.zigbee2mqtt/#).mqtt-publish— send a payload to a topic with configurable QoS and retain.
All skills auto-source the credentials file written by /mqtt-setup, so connection details never need to be re-supplied.
Requirements
mosquitto-clients on the local machine:
sudo apt install mosquitto-clients # Debian/Ubuntu
brew install mosquitto # macOS
Installation
claude plugins marketplace add danielrosehill/Claude-Code-Plugins
claude plugins install mqtt-observability@danielrosehill
Then restart Claude Code and run /mqtt-setup to register your broker.
Credential storage
The plugin writes credentials to ~/.claude/plugins-data/mqtt-observability/credentials.env (mode 600, parent dir 700). The file is a plain shell-sourceable env file. To remove, delete the file or re-run /mqtt-setup.
License
MIT