Model Context Protocol moderate risk

Modbus

This MCP server provides a standardized interface for interacting with Modbus devices, enabling AI agents to read and write data to industrial control systems.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwrite

Quickstart

Config

{
   "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 },
       }
   }
}

Exposed MCP Tools (7)

safe

read_register

Reads the value of a Modbus holding register.

Read-only operation, no side effects.

moderate

write_register

Writes a value to a Modbus holding register.

Can modify device parameters, but not destructive if used carefully.

safe

read_coils

Reads the status of Modbus coils.

Read-only operation, no side effects.

moderate

write_coil

Writes a value to a Modbus coil.

Can control digital outputs, but not destructive if used carefully.

safe

read_input_registers

Reads the values of Modbus input registers.

Read-only operation, no side effects.

safe

read_multiple_holding_registers

Reads the values of multiple Modbus holding registers.

Read-only operation, no side effects.

safe

analyze_register

Analyzes Modbus register values with a customizable prompt.

Read-only operation, no side effects.

Safety Assessment

This MCP server is relatively safe for read-only operations and data analysis. However, write operations should be performed with caution, as they can directly impact industrial processes. Proper network security measures and configuration are crucial to mitigate risks.

Supports read-only operations for data retrieval.
Requires explicit configuration of Modbus parameters.
No direct internet exposure without proper network setup.
Limited scope of operations within the Modbus protocol.

Allows write operations to Modbus registers and coils, potentially affecting industrial processes.
No built-in authentication or access control beyond Modbus's inherent limitations.
Incorrect configuration can lead to unintended changes in device behavior.
Vulnerable to Modbus-specific attacks if not properly secured at the network level.