plc-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 | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_tagA | Read a PLC tag value. Returns the current value of the specified tag. |
| read_tagsA | Read multiple PLC tags at once. More efficient than multiple single reads. |
| write_tagA | Write a value to a PLC tag. Requires write permissions and tag must be in whitelist. |
| list_tagsB | List all available tags in the PLC. Can filter by pattern. |
| get_alarmsB | Get active alarms from the PLC. |
| acknowledge_alarmC | Acknowledge an active alarm. |
| get_plc_statusA | Get PLC status including CPU state, mode, and faults. |
| get_io_statusC | Get I/O module status and health. |
| get_connection_infoC | Get connection information and statistics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Tag Database | Complete list of PLC tags with metadata |
| Alarm Configuration | Alarm definitions and thresholds |
TDQS
Scored across 9 tools
Each tool targets a distinct action: reading/writing tags, listing tags, managing alarms, or retrieving status info. No overlap in purpose.
All tools follow a consistent verb_noun pattern using snake_case (e.g., read_tag, write_tag, acknowledge_alarm).
9 tools cover the essential PLC operations without unnecessary bloat; the count is well-scoped for the domain.
Core operations (read/write tags, list tags, alarms, status) are present; missing a bulk write or subscription feature, but these are minor gaps.