Forgeline
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Forgelineread holding registers from address 0 to 4"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Forgeline
Read-only Modbus TCP monitoring, exposed as safe MCP tools.
Forgeline is an MCP server that lets an AI agent monitor an industrial Modbus TCP device — read holding/input registers, coils, and device identity — without any ability to change it.
Safety by design. This MVP exposes read-only tools only. There are no write/command tools, and no helper code exists to write coils or registers. An agent connected to Forgeline cannot alter device state.
A simulated Modbus device is bundled, so you can run the whole thing with zero hardware.
Status
MVP complete. All four read-only tools — get_device_info,
read_holding_registers, read_input_registers, and read_coils — are
implemented and verified end-to-end against the bundled simulator.
Related MCP server: KVMFleet MCP Server
Project layout
forgeline/
├── src/forgeline/
│ ├── server.py # FastMCP server: registers MCP tools
│ └── tools.py # Read-only Modbus implementations (transport-agnostic)
├── simulator/
│ └── device.py # Bundled pymodbus TCP simulator (zero hardware)
├── docker-compose.yml # Starts simulator + server together
├── Dockerfile
├── pyproject.toml
├── README.md
└── LICENSE # Apache 2.0Quick start
Option A — Docker (simulator + server, one command)
docker compose up --buildThis starts:
simulator — a virtual Modbus device on
localhost:5020.forgeline — the MCP server over
streamable-httpathttp://localhost:8000/mcp, already pointed at the simulator.
Option B — Local Python
Requires Python 3.10+.
pip install -e .
# Terminal 1: start the bundled simulator
forgeline-simulator
# Terminal 2: run the MCP server (stdio transport, for an MCP client)
forgelineBy default the server talks to the simulator on 127.0.0.1:5020.
Configuration
All configuration is via environment variables.
Variable | Default | Description |
|
| Host of the Modbus TCP device to monitor. |
|
| Port of the Modbus TCP device. |
|
| Modbus unit / slave id. |
|
| Per-request timeout in seconds. |
|
| MCP transport: |
|
| Bind host for HTTP transports. |
|
| Bind port for HTTP transports. |
|
| Bind host for the bundled simulator. |
|
| Bind port for the bundled simulator. |
Connecting an MCP client
To launch Forgeline over stdio (e.g. from Claude Desktop or another MCP client),
register a server that runs the forgeline command. Example client config:
{
"mcpServers": {
"forgeline": {
"command": "forgeline",
"env": { "MODBUS_HOST": "127.0.0.1", "MODBUS_PORT": "5020" }
}
}
}(Start forgeline-simulator first, or point MODBUS_HOST/MODBUS_PORT at a
real device.)
Tools
get_device_info
Returns identity and connection details for the monitored device.
{
"host": "127.0.0.1",
"port": 5020,
"unit_id": 1,
"connected": true,
"device_identification_supported": true,
"identity": {
"vendor_name": "Forgeline",
"product_code": "FL-SIM-1",
"revision": "1.0.0",
"vendor_url": "https://github.com/codenikhildr/Forgeline",
"product_name": "Forgeline Modbus Simulator",
"model_name": "Virtual PLC",
"user_application_name": "Forgeline MVP Simulator"
}
}Devices that do not implement Modbus device identification still return
connection details, with device_identification_supported: false.
read_holding_registers / read_input_registers
Read 16-bit registers — holding (FC 0x03, read/write on the device) or input (FC 0x04, read-only measurements). Parameters:
Param | Type | Default | Bounds |
| int | — |
|
| int |
|
|
// read_holding_registers(address=0, count=5)
{
"start_address": 0,
"count": 5,
"unit_id": 1,
"values": [
{ "address": 0, "value": 100 },
{ "address": 1, "value": 101 },
{ "address": 2, "value": 102 },
{ "address": 3, "value": 103 },
{ "address": 4, "value": 104 }
]
}read_coils
Read single-bit on/off coils (FC 0x01). Parameters:
Param | Type | Default | Bounds |
| int | — |
|
| int |
|
|
// read_coils(address=0, count=4)
{
"start_address": 0,
"count": 4,
"unit_id": 1,
"values": [
{ "address": 0, "value": false },
{ "address": 1, "value": true },
{ "address": 2, "value": false },
{ "address": 3, "value": true }
]
}Requests outside these bounds (count over the limit, or a range that exceeds the 16-bit address space) are rejected before any request reaches the device.
Simulator data map
The bundled simulator pre-populates each table (addresses are zero-based):
Table | FC | Addresses | Values |
Holding registers | 0x03 | 0–99 |
|
Input registers | 0x04 | 0–99 |
|
Coils | 0x01 | 0–99 |
|
Discrete inputs | 0x02 | 0–99 |
|
Development
Run the test suite — it starts the bundled simulator on a test port and exercises all four tools plus the input-validation guards:
pip install -e ".[dev]"
pytestCI runs the same suite on every push and pull request across Python 3.10–3.12.
License
Apache License 2.0. See LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
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/codenikhildr/Forgeline'
If you have feedback or need assistance with the MCP directory API, please join our Discord server