Skip to main content
Glama
jettydiot
by jettydiot
README.md
# @jettyd/mcp

MCP server for [jettyd](https://jettyd.com) — gives AI agents direct access to IoT devices.

Connect Claude Desktop, Cursor, Continue, or any MCP-compatible client to your ESP32 devices.

## Install

```bash
npx @jettyd/mcp
```

Or globally:
```bash
npm install -g @jettyd/mcp
```

## Setup

### Claude Desktop

Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "jettyd": {
      "command": "npx",
      "args": ["@jettyd/mcp"],
      "env": {
        "JETTYD_API_KEY": "your-api-key-here"
      }
    }
  }
}
```

### Cursor / Continue

Add to your MCP config:
```json
{
  "jettyd": {
    "command": "npx @jettyd/mcp",
    "env": { "JETTYD_API_KEY": "your-api-key" }
  }
}
```

## Tools

| 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 |

## Example conversations

> **"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_command` with `relay.on` and `{duration: 30000}`

> **"Alert me if temperature goes above 30°C"**
> → Calls `push_rules` with a threshold rule

> **"Show me the humidity trend for the last 24 hours"**
> → Calls `get_telemetry` with metric=air.humidity, period=24h

## Get your API key

Sign up at [jettyd.com](https://jettyd.com) and get your API key from the dashboard.

## Complete Setup Guide

New to jettyd? The [OpenClaw Blueprint](BLUEPRINT.md) walks through the complete setup in 6 steps — hardware, platform, OpenClaw connection, sensors, automations, and dashboard.

## Source

[github.com/jettydiot/jettyd-mcp](https://github.com/jettydiot/jettyd-mcp)

MIT licence

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of device interaction: listing devices, reading current state, sending commands, fetching historical data, and managing automation rules. No two tools have overlapping purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (list_devices, read_device, send_command, get_telemetry, push_rules). Predictable and uniform.

Tool Count5/5

5 tools is well-scoped for an IoT device management server, covering essential operations without redundancy or bloat.

Completeness4/5

The set covers listing, reading, commanding, telemetry, and rule automation, which are core for IoT interaction. Device create/update/delete are absent but likely outside the server's scope of managing existing devices.

Maintenance

ActivityInactive
ResponsivenessNo issues