Connect AI agents to IoT devices — read sensors, send commands, manage ESP32 fleets.
MCP server for jettyd — gives AI agents direct access to IoT devices.
Connect Claude Desktop, Cursor, Continue, or any MCP-compatible client to your ESP32 devices.
npx @jettyd/mcp
Or globally:
npm install -g @jettyd/mcp
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"jettyd": {
"command": "npx",
"args": ["@jettyd/mcp"],
"env": {
"JETTYD_API_KEY": "your-api-key-here"
}
}
}
}
Add to your MCP config:
{
"jettyd": {
"command": "npx @jettyd/mcp",
"env": { "JETTYD_API_KEY": "your-api-key" }
}
}
| Tool | Description |
|---|---|
list_devices | List all devices with status |
read_device | Get current sensor readings |
send_command | Send command to device (relay, LED, etc.) |
get_telemetry | Historical sensor readings |
push_rules | Push JettyScript automation rules |
"What's the temperature in the greenhouse?" → Calls
read_device, reads shadow, returns current temperature
"Turn on the irrigation relay for 30 seconds" → Calls
send_commandwithrelay.onand{duration: 30000}
"Alert me if temperature goes above 30°C" → Calls
push_ruleswith a threshold rule
"Show me the humidity trend for the last 24 hours" → Calls
get_telemetrywith metric=air.humidity, period=24h
Sign up at jettyd.com and get your API key from the dashboard.
New to jettyd? The OpenClaw Blueprint walks through the complete setup in 6 steps — hardware, platform, OpenClaw connection, sensors, automations, and dashboard.
github.com/jettydiot/jettyd-mcp
MIT licence
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @jettyd/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-jettyd-mcp": {
"command": "npx",
"args": [
"-y",
"@jettyd/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@jettyd/mcpnpmcom.jettyd/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.