EMQX Cloud MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMQXCLOUD_MQTT_PASSWORD | No | Optional password reference for authentication write tools. Additional suffixed variants such as EMQXCLOUD_MQTT_PASSWORD_DEVICE_A may be used. | |
| EMQXCLOUD_PLATFORM_API_KEY | No | Platform API key. | |
| EMQXCLOUD_PLATFORM_ENDPOINT | No | Platform API endpoint. Must end with /public_api/v1, use HTTPS, and contain no URL credentials, queries, or fragments. | |
| EMQXCLOUD_DEPLOYMENT_API_KEY | No | Deployment API key (App ID). | |
| EMQXCLOUD_DEPLOYMENT_ENDPOINT | No | Deployment API endpoint. Must end with /api/v5, use HTTPS, and contain no URL credentials, queries, or fragments. | |
| EMQXCLOUD_PLATFORM_API_SECRET | No | Platform API secret. | |
| EMQXCLOUD_DEPLOYMENT_API_SECRET | No | Deployment API secret (App Secret). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List projects visible to this connection's Platform API key. |
| list_deploymentsA | List deployments visible to this connection's Platform API key. |
| get_deploymentB | Read actual deployment status. Poll at most once per minute until running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct resource and action: list_projects (projects), list_deployments (deployments), and get_deployment (single deployment status). There is no overlap between them, so an agent can select correctly with confidence.
All three tools follow a clean verb_noun snake_case pattern (list_projects, list_deployments, get_deployment). The convention is uniform and predictable.
Three read-only tools is thin for a deployment-management server that implies lifecycle operations. It is borderline rather than broken, but the surface feels under-scoped for the domain.
Only read/list operations exist: there is no create, update, delete, or restart deployment, and no access to credentials, metrics, or connection details. Agents managing EMQX Cloud deployments will hit dead ends for any mutating or monitoring workflow.