Energyatit vs Jettyd MCP
A side-by-side look at the Energyatit 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 Energyatit 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 Energyatit when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ENERGYATIT_API_KEY, ENERGYATIT_TOKEN, ENERGYATIT_BASE_URL.
Choose Jettyd MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- 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 | 39/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | ENERGYATIT_API_KEYENERGYATIT_TOKENENERGYATIT_BASE_URL | JETTYD_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Energyatit | View Jettyd MCP |
Tools & capabilities
Energyatit 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.
Energyatit
{
"mcpServers": {
"energyatit": {
"command": "npx",
"args": [
"-y",
"energyatit-mcp-server"
],
"env": {
"ENERGYATIT_API_KEY": "YOUR_ENERGYATIT_API_KEY_HERE",
"ENERGYATIT_TOKEN": "YOUR_ENERGYATIT_TOKEN_HERE",
"ENERGYATIT_BASE_URL": "YOUR_ENERGYATIT_BASE_URL_HERE"
}
}
}
}
Jettyd MCP
{
"mcpServers": {
"mcp-103": {
"command": "npx",
"args": [
"-y",
"@jettyd/mcp"
],
"env": {
"JETTYD_API_KEY": "YOUR_JETTYD_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Energyatit is categorized under Industrial & IoT and uses a local stdio subprocess. Jettyd MCP belongs to Industrial & IoT and uses a local stdio subprocess. Pick Energyatit 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.
Energyatit has no declared pricing — check the project's own site. Jettyd MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 energyatit and mcp-103 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Energyatit has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Jettyd MCP has 52/100 (Good) with 4 views, 0 installs and 0 GitHub stars.