@jettyd/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JETTYD_API_KEY | Yes | Your jettyd API key. Get it from https://jettyd.com dashboard. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List all IoT devices in your jettyd account with their current status and last seen time. |
| read_deviceB | Get the current sensor readings and state for a specific device. |
| send_commandB | Send a command to a device (e.g. turn on a relay, blink an LED, set a value). |
| get_telemetryB | Get historical sensor readings for a device over a time period. |
| push_rulesA | Push JettyScript automation rules to a device. Rules run on-device and can trigger alerts when sensor thresholds are crossed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
All tool names follow a consistent verb_noun pattern (list_devices, read_device, send_command, get_telemetry, push_rules). Predictable and uniform.
5 tools is well-scoped for an IoT device management server, covering essential operations without redundancy or bloat.
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.