Modbus Integration
STDIOStandardizes and contextualizes Modbus data for AI agent integration with industrial IoT systems.
Standardizes and contextualizes Modbus data for AI agent integration with industrial IoT systems.
An MCP server that standardizes and contextualizes Modbus data, enabling seamless integration of AI agents with industrial IoT systems.
read_register
, write_register
).read_coils
, write_coil
).read_input_registers
).read_multiple_holding_registers
).analyze_register
).Install uv
:
curl -LsSf https://astral.sh/uv/install.sh | sh
Clone the Repository:
git clone https://github.com/kukapay/modbus-mcp.git cd modbus-mcp
Install Dependencies:
uv sync
The server connects to a Modbus device using parameters specified via environment variables. Set these variables in a .env
file or your shell environment.
Variable | Description | Default | Required |
---|---|---|---|
MODBUS_TYPE | Connection type: tcp , udp , or serial | tcp | Yes |
MODBUS_HOST | Host address for TCP/UDP | 127.0.0.1 | For TCP/UDP |
MODBUS_PORT | Port for TCP/UDP | 502 | For TCP/UDP |
MODBUS_DEFAULT_SLAVE_ID | Slave ID | 1 | For TCP/UDP |
MODBUS_SERIAL_PORT | Serial port (e.g., /dev/ttyUSB0 , COM1 ) | /dev/ttyUSB0 | For serial |
MODBUS_BAUDRATE | Serial baud rate | 9600 | For serial |
MODBUS_PARITY | Serial parity: N (none), E (even), O (odd) | N | For serial |
MODBUS_STOPBITS | Serial stop bits | 1 | For serial |
MODBUS_BYTESIZE | Serial byte size | 8 | For serial |
MODBUS_TIMEOUT | Serial timeout (seconds) | 1 | For serial |
.env
FileFor TCP:
MODBUS_TYPE=tcp
MODBUS_HOST=192.168.1.100
MODBUS_PORT=502
MODBUS_SLAVE_ID=1
For Serial:
MODBUS_TYPE=serial
MODBUS_SERIAL_PORT=/dev/ttyUSB0
MODBUS_BAUDRATE=9600
MODBUS_PARITY=N
MODBUS_STOPBITS=1
MODBUS_BYTESIZE=8
MODBUS_TIMEOUT=1
The configuration file:
{ "mcpServers": { "Modbus MCP Server": { "command": "uv", "args": [ "--directory", "/path/to/modbus-mcp", "run", "modbus-mcp" ], "env": { "MODBUS_TYPE": "tcp", "MODBUS_HOST": "127.0.0.1", "MODBUS_PORT": 502 }, } } }
Note: Natural language support depends on the client’s ability to parse and map prompts to tools. The MCP Inspector requires structured JSON, but the examples below show how conversational inputs translate.
Read a Holding Register:
Please read the value of Modbus holding register 0.
{ "tool": "read_register", "parameters": {"address": 0, "slave_id": 1} }
Value: <register_value>
Write to a Holding Register:
Set Modbus holding register 10 to the value 100.
{ "tool": "write_register", "parameters": {"address": 10, "value": 100, "slave_id": 1} }
Successfully wrote 100 to register 10
Read Coils:
Check the status of the first 5 Modbus coils starting at address 0.
{ "tool": "read_coils", "parameters": {"address": 0, "count": 5, "slave_id": 1} }
Coils 0 to 4: [False, False, False, False, False]
Write to a Coil:
Turn on Modbus coil 5.
{ "tool": "write_coil", "parameters": {"address": 5, "value": true, "slave_id": 1} }
Successfully wrote True to coil 5
Read Input Registers:
Read the values of 3 Modbus input registers starting from address 2.
{ "tool": "read_input_registers", "parameters": {"address": 2, "count": 3, "slave_id": 1} }
Input Registers 2 to 4: [<value1>, <value2>, <value3>]
Read Multiple Holding Registers:
Get the values of Modbus holding registers 0 through 2.
{ "tool": "read_multiple_holding_registers", "parameters": {"address": 0, "count": 3, "slave_id": 1} }
Holding Registers 0 to 2: [<value1>, <value2>, <value3>]
This project is licensed under the MIT License. See LICENSE for details.