Before using the EMQX MCP Server tools, you need to set up an EMQX cluster with properly configured API Key and client authentication. There are
Before using the EMQX MCP Server tools, you need to set up an EMQX cluster with properly configured API Key and client authentication. There are several options:. Exposed over MCP by the emqx mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
list_mqtt_clients — The list_mqtt_clients tool exposed by this serverget_mqtt_client — The get_mqtt_client tool exposed by this serverkick_mqtt_client — The kick_mqtt_client tool exposed by this serverpublish_mqtt_message — The publish_mqtt_message tool exposed by this serversubscribe_mqtt_topic — The subscribe_mqtt_topic tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 3 environment variables: EMQX_API_URL, EMQX_API_KEY, EMQX_API_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Emqx's toolset — list_mqtt_clients, get_mqtt_client, kick_mqtt_client and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Benniu; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Emqx's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_mqtt_clients | The list_mqtt_clients tool exposed by this server. |
| get_mqtt_client | The get_mqtt_client tool exposed by this server. |
| kick_mqtt_client | The kick_mqtt_client tool exposed by this server. |
| publish_mqtt_message | The publish_mqtt_message tool exposed by this server. |
| subscribe_mqtt_topic | The subscribe_mqtt_topic tool exposed by this server. |
{
"mcpServers": {
"emqx": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"EMQX_API_URL": "your-value",
"EMQX_API_KEY": "your-value",
"EMQX_API_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| EMQX_API_URL | Endpoint or connection string the server talks to. | Yes |
| EMQX_API_KEY | Credential the server authenticates with. | Yes |
| EMQX_API_SECRET | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.