Shelly Cloud (BYOK)

Shelly Cloud (BYOK) — connector documentation

• MCP endpoint: https://byok-shelly-cloud-control.connectorbay.com/mcp
• REST API: POST https://byok-shelly-cloud-control.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-shelly-cloud-control.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Shelly Cloud Shelly Cloud authorization key (User settings, Authorization cloud key), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-shelly-cloud-control.connectorbay.com/health · Tool schemas: https://byok-shelly-cloud-control.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-shelly-cloud-control · agent@connectorbay.com

What Shelly Cloud (BYOK) is for

Shelly Cloud (BYOK) lets an AI assistant read your own Shelly Cloud devices and, with your approval of each change, change their state through the Shelly Cloud API with a key you supply (Shelly Cloud authorization key (User settings, Authorization cloud key)). Read tools plus 4 device-changing tools (set_switch, set_light_power, set_light_white, set_light_color); each change runs only when confirm is yes, after you approved it in chat. 6 tools in all (get_device_info, get_component_status, set_switch, set_light_power, set_light_white, set_light_color). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.shelly.cloud. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Shelly Cloud. Shelly Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Is my Shelly device b48a0a1cd978 online?"
• "What is the power draw of switch:0 on my Shelly device b48a0a1cd978?"
• "Turn off the Shelly plug b48a0a1cd978"
• "Turn on the Shelly light b48a0a1cd978"
• "Set my Shelly bulb b48a0a1cd978 to 50 percent warm white"
• "Make my Shelly RGBW light b48a0a1cd978 green"

What it does

• get_device_info: Get the basic record of one Shelly device: id, type, model code, generation and whether it is online. Limited to one call per second.
• get_component_status: Get the status of one component of a Shelly device, for example switch:0 (output, power, voltage, energy), light:0, input:0, temperature:0 or sys. Limited to one call per second.
• set_switch: Switch one relay channel of a Shelly relay or plug on or off, optionally switching back after a number of seconds. Use only for lamps, plugs and similar loads; do not use it for a door, gate, lock, alarm, boiler or gas appliance. This changes the physical device.
• set_light_power: Switch one channel of a Shelly light or dimmer on or off, optionally switching back after a number of seconds. Use only for lamps, plugs and similar loads; do not use it for a door, gate, lock, alarm, boiler or gas appliance. This changes the physical device.
• set_light_white: Put a Shelly light in white mode with a brightness and an optional color temperature. Use only for lamps, plugs and similar loads; do not use it for a door, gate, lock, alarm, boiler or gas appliance. This changes the physical device.
• set_light_color: Put a Shelly RGB light in color mode with red, green and blue values and an optional gain. Use only for lamps, plugs and similar loads; do not use it for a door, gate, lock, alarm, boiler or gas appliance. This changes the physical device.

BYOK key

You bring your own Shelly Cloud Shelly Cloud authorization key (User settings, Authorization cloud key) (https://shelly-api-docs.shelly.cloud/cloud-control-api/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.shelly.cloud over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://shelly-api-docs.shelly.cloud/cloud-control-api/communication-v2/ (the API this connector calls, with a BYOK key)

Live from the Shelly Cloud API (*.shelly.cloud) with a BYOK key; documentation: https://shelly-api-docs.shelly.cloud/cloud-control-api/communication-v2/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Shelly Cloud. Shelly Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with. It reads your Shelly Cloud data and can change device state only when a specific action is approved and confirmed (confirm = yes); it never deletes, resets, sends messages or creates paid resources.

Built for: Worldwide. Languages: English.

Shelly Cloud (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Shelly Cloud (BYOK) is. Shelly Cloud (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Shelly Cloud data: Read your Shelly device state and switch Shelly relays and lights (power, brightness, color, white temperature) through Shelly Cloud with your own authorization key. You bring your own Shelly Cloud Shelly Cloud authorization key (User settings, Authorization cloud key); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Shelly Cloud call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to *.shelly.cloud, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Shelly Cloud rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Shelly Cloud receives. The request we make on your behalf, including the key and the arguments, under Shelly Cloud's own terms and privacy policy. Shelly Cloud acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Shelly Cloud gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Shelly Cloud data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Shelly Cloud (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Shelly Cloud at any time to end all access.

Children. Shelly Cloud (BYOK) is a general-audience service operated by the adult using the assistant, under Shelly Cloud's own age rules.

Changes. We will post changes here with a new effective date.

Shelly Cloud (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Shelly Cloud (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Shelly Cloud (BYOK) provides: Read your Shelly device state and switch Shelly relays and lights (power, brightness, color, white temperature) through Shelly Cloud with your own authorization key. It is accessed through an AI assistant or directly over MCP or HTTP, and can read the device data and change device state, but only through actions you approve in chat and confirm.
2. Your own key, your own account. You must use your own Shelly Cloud credentials and only access data you are allowed to access. Shelly Cloud's terms apply to your use of Shelly Cloud; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Shelly Cloud. Shelly Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Shelly Cloud returns, lightly trimmed; it may be incomplete, delayed or changed by Shelly Cloud. Check important facts at the source.
5. Device changes. The Service changes the state of a Shelly Cloud device only through an action you approve in chat and pass with confirm = yes. It does not delete, reset, wipe, send messages or create paid resources.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Shelly Cloud's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Shelly Cloud may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Shelly Cloud key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Shelly Cloud takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-shelly-cloud-control

Shelly Cloud (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-shelly-cloud-control.connectorbay.com/mcp
• REST API: https://byok-shelly-cloud-control.connectorbay.com/openapi.json
• Live status: https://byok-shelly-cloud-control.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Shelly Cloud (BYOK) never asks for them.