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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/brayangcastro/mcp-industrial-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server