AIoT MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MQTT_PASSWORD | No | MQTT password (optional) | |
| MQTT_USERNAME | No | MQTT username (optional) | |
| MQTT_BROKER_URL | No | MQTT broker URL | mqtt://127.0.0.1:1883 |
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discoverA | Discover devices and rules in a group using MQTT topic filter. When asked status of a group, provide the device GROUP as the argument. If no group is provided, discover all devices and rules in the domain. |
| publishA | Publish a message to a device using MQTT topic and payload. When asked to control a device, you should use this tool with the topic argument discovered from the "discover" tool. For example, a device might describe itself subscribing to a topic livingroom/456/command, then this is the topic to be used to control the device. |
| queryA | When asked status of a device, provide the device TOPIC as the argument. The topic can be found in previous messages from the "discover" tool. For example, a device might describe itself publishing its status to a topic livingroom/456/status, then this is the topic to be used to query the status of the device. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| assistant |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: discover finds devices/rules, publish sends commands, query retrieves status. No overlap in functionality; the descriptions clearly differentiate them.
All tool names are single verbs in lowercase, following a consistent imperative style (discover, publish, query). No mixing of conventions or styles.
Three tools is well-scoped for an MQTT-based AIoT server, covering discovery, control, and status query. Each tool earns its place without unnecessary bloat or missing core operations.
The core lifecycle of discovering, controlling, and querying devices is covered. A minor gap is the lack of explicit rule management (create/update/delete), but rules are discovered via the discover tool, and the primary IoT interactions are complete.