Forgeline
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODBUS_HOST | No | Host of the Modbus TCP device to monitor. | 127.0.0.1 |
| MODBUS_PORT | No | Port of the Modbus TCP device. | 5020 |
| FORGELINE_HOST | No | Bind host for HTTP transports. | 127.0.0.1 |
| FORGELINE_PORT | No | Bind port for HTTP transports. | 8000 |
| MODBUS_TIMEOUT | No | Per-request timeout in seconds. | 3.0 |
| MODBUS_UNIT_ID | No | Modbus unit / slave id. | 1 |
| SIMULATOR_HOST | No | Bind host for the bundled simulator. | 0.0.0.0 |
| SIMULATOR_PORT | No | Bind port for the bundled simulator. | 5020 |
| FORGELINE_TRANSPORT | No | MCP transport: stdio, sse, or streamable-http. | stdio |
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 |
|---|---|
| get_device_infoA | Get identity and connection details for the monitored Modbus device. Returns the device's vendor, product code, revision and related fields (when the device supports Modbus device identification), plus the host, port and unit id Forgeline is connected to. Read-only. |
| read_holding_registersB | Read holding registers (FC 0x03) from the monitored Modbus device. Holding registers are 16-bit read/write values (Forgeline reads them only). Returns the start address, count, unit id, and a list of address -> value pairs. Read-only. |
| read_input_registersA | Read input registers (FC 0x04) from the monitored Modbus device. Input registers are 16-bit read-only measurements. Returns the start address, count, unit id, and a list of address -> value pairs. |
| read_coilsA | Read coils (FC 0x01) from the monitored Modbus device. Coils are single-bit on/off values. Returns the start address, count, unit id, and a list of address -> boolean value pairs. Read-only. |
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 4 tools
Each tool has a distinct purpose: get_device_info for identity/connection, read_coils for single-bit values, read_holding_registers for 16-bit read/write registers, and read_input_registers for 16-bit read-only registers. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., get_device_info, read_coils). The naming convention is uniform and predictable.
With 4 tools, the server is well-scoped for its purpose of monitoring a Modbus device. The count is within the ideal range of 3-15 tools and covers essential read operations without unnecessary bloat.
The tool set covers device identity and the three primary read function codes (coils, holding registers, input registers) for Modbus monitoring. A minor gap is the absence of reading discrete inputs (FC 0x02), but this is a reasonable omission for a basic monitoring server.