IoT Diagnosis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MQTT_ENABLED | No | Set to 'true' to enable MQTT subscription for device status, telemetry, logs, fault, and heartbeat topics. | false |
| MODEL_CACHE_MODE | No | Model cache mode: 'download' allows fetching missing models from the network; 'offline' blocks downloads and fails readiness if the cache is incomplete. | download |
| DIAGNOSIS_LLM_MODEL | No | Model identifier for the external LLM used for complex diagnosis. | |
| DIAGNOSIS_LLM_API_KEY | No | API key for the external LLM used for complex diagnosis (if unset, heuristic fallback is used). | |
| DIAGNOSIS_DATABASE_PATH | No | Path to the SQLite database used as the local source of truth. | data/iot_diagnosis.db |
| DIAGNOSIS_MCP_PUBLIC_URL | No | Public URL of the MCP server, used by clients and required when a bearer token is set. | |
| DIAGNOSIS_MCP_BEARER_TOKEN | No | If set, the MCP endpoint requires this Bearer token for authentication. | |
| DIAGNOSIS_SYNC_RETRY_SECONDS | No | Interval in seconds for retrying failed MySQL/Qdrant writes via the persisted outbox. | |
| DIAGNOSIS_RETRIEVAL_MODEL_HEALTH_URL | No | Health check URL for the retrieval model service, used by the /ready endpoint. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues