Bigiron vs Jettyd MCP
A side-by-side look at the Bigiron 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 Bigiron for industrial & iot work as a local process; 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 Bigiron when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You want tools like
bigiron_search, bigiron_sold_search, bigiron_lot_detail.
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 | 52/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | JETTYD_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View Bigiron | View Jettyd MCP |
Tools & capabilities
Bigiron tools 3
bigiron_searchActive listings for a keyword query: current bid, Buy-It-Now asking price (if offered), make/model/year, seller, location, category, auction close time.bigiron_sold_searchConfirmed-SOLD lots for a keyword query, newest closes first: title, make/model/year, quantity, seller, location, close date, bid count. `final_price` is always `null` — see the price gap below.bigiron_lot_detailFull detail for one lot by URL slug: description, sale status, bid count, make/model/year, seller, location, category and (for active lots) current bid / Buy-It-Now price.
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.
Bigiron
{
"mcpServers": {
"bigiron": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bigiron"
]
}
}
}
Jettyd MCP
{
"mcpServers": {
"mcp-103": {
"command": "npx",
"args": [
"-y",
"@jettyd/mcp"
],
"env": {
"JETTYD_API_KEY": "YOUR_JETTYD_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Bigiron is categorized under Industrial & IoT and uses a local stdio subprocess. Jettyd MCP belongs to Industrial & IoT and uses a local stdio subprocess. Pick Bigiron 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.
Bigiron has no declared pricing — check the project's own site. 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 bigiron and mcp-103 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bigiron has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Jettyd MCP has 48/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.