industrial-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INDUSTRIAL_MCP_ADAPTER | No | Select the adapter backend. Default is 'mock'. Other options like 'mqtt' or 'rest' can be implemented. | |
| INDUSTRIAL_MCP_ALLOW_WRITES | No | Set to 'true' to allow live (non-dry-run) execution of write tools like trigger_motor_action. Default is off (read-only). |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_plantsA | List industrial facilities the server can see. |
| list_silosB | List grain silos at a plant, with capacity in metric tons. |
| get_silo_thermometryA | Return the latest thermometry snapshot for one silo. Includes fill percent, cable count, and min/max/avg grain temperature in Celsius. Use this when the operator asks about a specific silo's health. |
| list_motorsA | List motors at a plant. Optionally filter by kind. |
| get_active_alertsA | List active alerts at a plant, optionally filtered by minimum severity. |
| trigger_motor_actionA | Request a start or stop of an industrial motor. Defaults to a DRY RUN: returns what would happen, evaluates safety preconditions, and lists warnings — without sending any command to the field. To actually execute:
Every executed command is appended to an audit log; dry-run calls are not logged. |
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 6 tools
Each tool targets a distinct resource and action: plants, silos, thermometry, motors, alerts, and motor actions. The only possible overlap is between list_silos and get_silo_thermometry, but one lists silos and the other retrieves data for a specific silo, so there is no ambiguity.
All tool names follow a consistent verb_noun pattern: list_plants, list_silos, list_motors, get_active_alerts, get_silo_thermometry, trigger_motor_action. The verbs are clear and the style is uniformly snake_case, making the set predictable and easy to navigate.
With 6 tools, the server is well-scoped for industrial monitoring and control. Each tool serves a clear purpose without excessive overlap or unnecessary additions, and the count is neither too thin nor too heavy for the domain.
The tool set covers the core workflows: listing assets, retrieving detailed sensor data, checking alerts, and issuing motor control commands with safety checks. Minor gaps exist, such as no dedicated tool for getting a single motor's detailed status or acknowledging alerts, but these do not critically hinder agent operations.