Jettyd MCP vs PLCs.ai
A side-by-side look at the Jettyd MCP and PLCs.ai MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jettyd MCP for industrial & iot work as a local process; choose PLCs.ai for industrial & iot over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose PLCs.ai when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 48/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | JETTYD_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Jettyd MCP | View PLCs.ai |
Tools & capabilities
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
PLCs.ai tools
No tool names declared yet. Check the project README from the listing page.
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.
Jettyd MCP
{
"mcpServers": {
"mcp-103": {
"command": "npx",
"args": [
"-y",
"@jettyd/mcp"
],
"env": {
"JETTYD_API_KEY": "YOUR_JETTYD_API_KEY_HERE"
}
}
}
}
PLCs.ai
{
"mcpServers": {
"plcs-ai": {
"url": "https://mcp.plcs.ai/mcp"
}
}
}
Frequently asked questions
Jettyd MCP is categorized under Industrial & IoT and uses a local stdio subprocess. PLCs.ai belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick Jettyd MCP for industrial & iot work and PLCs.ai 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.
Jettyd MCP has no declared pricing — check the project's own site. PLCs.ai 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 mcp-103 and plcs-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jettyd MCP has a quality signal of 48/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. PLCs.ai has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.