Modbus MCP vs Jettyd MCP
A side-by-side look at the Modbus MCP and Jettyd MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Modbus MCP for industrial & iot work; choose Jettyd MCP for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Modbus MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MODBUS_TYPE, MODBUS_HOST, MODBUS_PORT, MODBUS_DEFAULT_SLAVE_ID, MODBUS_SERIAL_PORT, MODBUS_BAUDRATE, MODBUS_PARITY, MODBUS_STOPBITS.
Choose Jettyd MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
JETTYD_API_KEY. - You want tools like
list_devices, read_device, send_command.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 33/100 · Emerging | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | MODBUS_TYPEMODBUS_HOSTMODBUS_PORTMODBUS_DEFAULT_SLAVE_IDMODBUS_SERIAL_PORTMODBUS_BAUDRATEMODBUS_PARITYMODBUS_STOPBITS | JETTYD_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 25 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Modbus MCP | View Jettyd MCP |
Tools & capabilities
Modbus MCP tools
No tool names declared yet. Check the project README from the listing page.
Jettyd MCP tools 5
list_devicesList all devices with statusread_deviceGet current sensor readingssend_commandSend command to device (relay, LED, etc.)get_telemetryHistorical sensor readingspush_rulesPush JettyScript automation rules
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Modbus MCP
No confirmed install command for Modbus MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Jettyd MCP
{
"mcpServers": {
"mcp-103": {
"command": "npx",
"args": [
"-y",
"@jettyd/mcp"
],
"env": {
"JETTYD_API_KEY": "YOUR_JETTYD_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Modbus MCP is categorized under Industrial & IoT and uses an install path we have not confirmed yet. Jettyd MCP belongs to Industrial & IoT and uses a local stdio subprocess. Pick Modbus MCP for industrial & iot work and Jettyd MCP for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Modbus MCP has no confirmed install command yet — follow its own setup instructions.
Modbus MCP is listed as free. Auth: no auth required. Jettyd MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kukapay-modbus-mcp and mcp-103 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Modbus MCP has a quality signal of 33/100 (Emerging) with 4 views, 0 installs and 25 GitHub stars. Jettyd MCP has 48/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.