An MCP server that standardizes and contextualizes Modbus data, enabling seamless integration of AI agents with industrial IoT systems.e
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-kukapay-modbus-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Modbus MCP Server An MCP server that standardizes and contextualizes Modbus data, enabling seamless integration of AI agents with industrial IoT systems.    ## Features - **Modbus Tools**: - Read/write holding registers (`read_register`, `write_register`). - Read/write coils (`read_coils`, `write_coil`). - Read input registers (`read_input_registers`). - Read multiple holding registers (`read_multiple_holding_registers`). - **Prompt**: Analyze Modbus register values with a customizable prompt (`analyze_register`). - **Flexible Connections**: Supports Modbus over TCP, UDP, or serial, configured via environment variables. ## Requirements - **Python**: 3.10 - **uv** for dependency and virtual environment management. ## Installation 1. **Install `uv`**: ```bash curl -LsSf https://astral.sh/uv/install.sh | sh ``` 2. **Clone the Repository**: ```bash git clone https://github.com/kukapay/modbus-mcp.git cd modbus-mcp ``` 3. **Install Dependencies**: ```bash uv sync ``` ## Configuration The server connects to a Modbus device using parameters specified via environment variables. Set these variables in a `.env` file or your shell environment. ### Environment Variables | 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…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.