Summary
Watch a live topic and publish onto it from the same place you are diagnosing the problem.
The timed subscription is what makes this a debugging tool rather than an admin panel: you listen to a topic for a bounded window, see what is actually flowing, and can publish a test message onto it without wiring up a client.
What it is
A server over an EMQX MQTT broker: connected clients listed and inspected, problem clients disconnected, messages published, and topics subscribed to over Server-Sent Events.
What you get
- Connected clients listed with paging, and filters on node, username, client ID, IP address, connection state, clean-start flag and protocol version
- Fuzzy filters on client ID, username and IP for when you only have part of the string
- Full detail on one client
- A client disconnected from the broker
- Messages published to any topic, with a QoS level of 0, 1 or 2 and an option to retain them for new subscribers
- A topic subscribed to for a bounded window, with a cap on how many messages to collect, parsed out of the SSE stream automatically
Requirements
An EMQX cluster you can reach — EMQX Cloud serverless or a self-hosted deployment.
Setup effort
One command plus a key — npx -y @smithery/cli install @Benniu/emqx-mcp-server --client claude, then supply credentials