CMMS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_production_ordersC | Get production orders from MES system. Can filter by status. |
| get_work_ordersB | Get work orders from MES system. Can filter by status or production order. |
| get_equipmentB | Get equipment status from MES system. Can filter by status or get specific equipment. |
| get_maintenance_tasksC | Get maintenance tasks from CMMS system. Can filter by status, priority, or type. |
| get_assetsC | Get assets from CMMS system. Can filter by status or get specific asset. |
| get_maintenance_historyB | Get maintenance history from CMMS system. Can filter by asset or date range. |
| create_maintenance_taskC | Create a new maintenance task in CMMS system. |
| get_sensorsC | Get sensors from IoT system. Can filter by type, status, or equipment. |
| get_sensor_readingsC | Get sensor readings from IoT system. Can filter by sensor, status, or time range. |
| get_devicesC | Get IoT devices. Can filter by status or type. |
| get_alertsB | Get IoT alerts. Can filter by severity, acknowledged status, or device. |
| acknowledge_alertC | Acknowledge an IoT alert. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| MES Production Orders | All production orders from MES system |
| MES Equipment | All equipment from MES system |
| CMMS Maintenance Tasks | All maintenance tasks from CMMS system |
| CMMS Assets | All assets from CMMS system |
| IoT Sensors | All sensors from IoT system |
| IoT Alerts | All active alerts from IoT system |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as acknowledging alerts, creating maintenance tasks, or retrieving various entities like assets, devices, equipment, and orders. There is no overlap or ambiguity in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern with underscores, such as 'acknowledge_alert', 'create_maintenance_task', and 'get_assets'. This uniformity enhances readability and predictability across the entire tool set.
With 12 tools, the count is well-scoped for a CMMS (Computerized Maintenance Management System) server that integrates IoT, MES, and maintenance workflows. Each tool serves a specific and necessary function without being excessive or insufficient for the domain.
The tool set provides comprehensive coverage for retrieving and creating key entities like alerts, tasks, assets, and orders, with good filtering options. However, there are minor gaps, such as missing update or delete operations for maintenance tasks or work orders, which agents might need to work around.